It does. It was code that was imported from a regular Flex component. It worked in the old app (although it was probably not necessary).
> On Jul 10, 2017, at 6:45 PM, Alex Harui <aha...@adobe.com.INVALID> wrote: > > If you have time, see if it works in regular Flex. > > Thanks, > -Alex > > On 7/10/17, 1:44 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.ap >>> ache.org%2FgYQ3&data=02%7C01%7C%7C24590c11840d4a15c0c308d4c76fe455%7Cfa7b >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636352730774030484&sdata=P%2BJlRLx >>> bAysbWrixSyA3wRVkBA3odVOIx5QrYlyCRLU%3D&reserved=0 >>> [2] >>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.ap >>> ache.org%2FOX9n&data=02%7C01%7C%7C24590c11840d4a15c0c308d4c76fe455%7Cfa7b >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636352730774030484&sdata=phzQNSX2J >>> YQTR7ImVBbezQ%2BKMLi9s0vXH4onQ%2BqSQuE%3D&reserved=0 >>> >>> >>> >>> >>> -- >>> View this message in context: >>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl >>> ex-development.2333347.n4.nabble.com%2FFlexJS-States-Bug-tp63028.html&dat >>> a=02%7C01%7C%7C24590c11840d4a15c0c308d4c76fe455%7Cfa7b1b5a7b34438794aed2c >>> 178decee1%7C0%7C0%7C636352730774030484&sdata=b3bhXSXxbQ5GOxIh2aM0oAV1AHjt >>> GCNKOUQNXUmK6SU%3D&reserved=0 >>> Sent from the Apache Flex Development mailing list archive at >>> Nabble.com. >> >
