Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enhancement request: Get value of control's property inside expression binding
See original GitHub issueHi,
When I’m defining a new control inside an XML-View , I’d like to be able to use the reference to that control and use the value of its certain property inside the expression binding.
Something like this:
...
property="{= thisControl.valueState === 'Error' ? _doThis_ : _doThat_ }"
...
Of course, I could just define an extra JSONModel and store the controls properties there in order to use it later in the expression binding, but that concept doesn’t work when I’m working with aggregation binding.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, I agree. Your pull request provides an answer to Boghyon’s question.
As I already commented, your suggestion is a general “enhancement to basic binding concepts which of course can be used inside expression binding, but not only there”. This is a good thing! But it means the tests are misplaced and we need other people’s approval as well, not just mine.
I like the idea of binding to another (or the own) control’s properties via a syntax similar to “model>path”. But: “@” is not a reserved character within a model name, e.g. “@i18n” is a perfectly valid model name as of today. I fear this change is somewhat incompatible. We need to find a better syntax.
Isn’t this very similar to the Pull Request https://github.com/SAP/openui5/pull/727 ?