ottobackwards commented on PR #755: URL: https://github.com/apache/plc4x/pull/755#issuecomment-1398554496
Thanks for the contribution! The issues with expression language for addresses and having multiple addresses in that property were at the time: - Putting something complicated to write in a text field is poor for the user - The original didn't use json, but used special character substitution changing the native addresses which was a no-go - The addresses / returns need to have their PLC types resolved, and if the address could change _every_ call ( which you have to assume if you use expression language ) then it would be good to have some kind of caching so that it wasn't so costly every time, and the original PR did not provide that *This PR to land would have to address the caching issue*. Having json addresses the "don't invent a custom addressing delimiter" issue. We would just have to live with how poor writing complicated json in that UI would be ( or doing it external and cut and pasting it in) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
