Just replying to the last mail of the thread.
I think a lot of other JS frameworks have the same set of problems. I think a
solution most of them use is to create internal ids based upon the id and the
id of the parent component.
In JSF for example they create these ids by this: “{parentId}:{id}” …
internally id lookups have to be adjusted, so if in a component a lookup for
“foo” is done, the compiler translates this to “{parentId}:foo”. This should
also make it quite easy to implement test-automation.
But I have no idea what downside this has (except for making the ids longer)
Chris
Am 21.05.17, 17:46 schrieb "piotrz" <[email protected]>:
More thinking about that we need for sure one property or pseudo property
which will resolve issue with "id" duplication, the other one for me is
something optional.
Piotr
-----
Apache Flex PMC
[email protected]
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61729.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
