Hi Mihia, I seen many posts relative to FLEX-34837 here and never had the time to discuss it, I've seen bug too in SDK 4.6 relative to getItemIndex when a collection is sorted and never had the time to check if it has been fixed later or not.
I have to admit I'm not very keen to see an already overly complex class to become even more complex adding complex field managment. I generally solve the problem at application level, using a decorator pattern to my VO mixed with a dynamic class to, at sort events, dynamicaly add or remove simple fields and forward their value to their complex counterpart, it works as well when you have hierarchical data and you want to display them in a flat datagrid, if those VO need to be sent on the server or the rest of the application, I use the decoratee VO. Simple , quiet efficient and get no risk to break this part of the framework already complex. Thought ? Frédéric THOMAS > From: mihai.ch...@gmail.com > Date: Fri, 29 May 2015 11:55:24 +0200 > Subject: Re: [GitHub] flex-sdk pull request: Fix FLEX-15159 by making > ArrayList extend P... > CC: dev@flex.apache.org > > >> 2. I have added my test to the "framework" project according to the wiki, > >> and it works! Except that there was already a > >> "frameworks/projects/framework/tests/ folder", and it already contained a > >> test (ListCollectionView_FLEX_34837_Tests.as). I suppose that this test was > >> not being run before, since the ANT infrastructure was not in place, and > >> now > >> that it is being run, it fails! Can I just mark this test as [Ignore] ? > > > > This is one of Mihai's. Maybe he remembers this test and it's > > relevance... I seem to remember he moved some of the tests a while > > ago, maybe this is something that's left over? > > This test is expected to fail, because the initial bug[1] is not yet > solved. I'll get to finishing it around next week. > > https://issues.apache.org/jira/browse/FLEX-34837
