The bug (if it is one) seems to be when using nested includeIn attributes. What happens is that you get two objects with the same key (i.e. the same object is included twice in the class)
> On Jul 10, 2017, at 11:07 AM, yishayw <yishayj...@hotmail.com> wrote: > > It looks like the compiler gets confused when we add nested objects using > state. This [1] is a test app that includes a [2] view, to demonstrate. > Should I file a bug? > > [1] https://paste.apache.org/gYQ3 > [2] https://paste.apache.org/OX9n > > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/FlexJS-States-Bug-tp63028.html > Sent from the Apache Flex Development mailing list archive at Nabble.com.
