flex-sdk

Clone Tools
  • last updated 18 mins ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add contributors list for 4.14.1

Add contributors list for 4.14.1

FLEX-34119 this unit test is blocking FlexUnit, so I'm moving it back (temporarily) to prevent it from being executed in the flex-sdk_test job until we find a solution for the stack overflow.

FLEX-34119 this unit test is blocking FlexUnit, so I'm moving it back (temporarily) to prevent it from being executed in the flex-sdk_test job until we find a solution for the stack overflow.

FLEX-34119 Running the over 10,000 parameterized tests in the ant test runner takes over an hour! (On my computer it only takes a bit above three minutes.) I'm ignoring this for now.

FLEX-34119 Running the over 10,000 parameterized tests in the ant test runner takes over an hour! (On my computer it only takes a bit above three minutes.) I'm ignoring this for now.

FLEX-34775 moved the unit test where it can be run by 'ant test'.

FLEX-34775 moved the unit test where it can be run by 'ant test'.

FLEX-34458 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34458 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34456 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34456 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34440 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34440 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34424 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-34424 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than a WindowedApplication, so I changed how uncaught client errors are captured to reflect this.

FLEX-43119 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than WindowedApplication, so I changed how uncaught client errors are captured.

FLEX-43119 moved the unit test where it can be run by 'ant test'. Also, the main test runner is an Application, rather than WindowedApplication, so I changed how uncaught client errors are captured.

FLEX-34778 moved the test to where it can be executed via 'ant test'

FLEX-34778 moved the test to where it can be executed via 'ant test'

FLEX-34119 our test runner seems to be an Application, rather than WindowedApplication. Now the unit test reflects that.

FLEX-34119 our test runner seems to be an Application, rather than WindowedApplication. Now the unit test reflects that.

FLEX-34119 renamed the test to the format expected by the ant test script.

FLEX-34119 renamed the test to the format expected by the ant test script.

FLEX-34119 moving the unit test to where it can be executed part of 'ant test'

FLEX-34119 moving the unit test to where it can be executed part of 'ant test'

FLEX-34778 running the unit tests as part of 'ant test' now, which implied moving them to frameworks/projects/advancedgrids/tests and changing the build scripts to allow test execution in the advancedgrids project.

FLEX-34778 running the unit tests as part of 'ant test' now, which implied moving them to frameworks/projects/advancedgrids/tests and changing the build scripts to allow test execution in the advancedgrids project.

FLEX-34778 CAUSE: When a node is opened, HierarchicalCollectionView starts to listen to changes to its children collection. And when it's closed, it doesn't stop listening to these CollectionEvents. So when a closed node's child is replaced, nestedCollectionChangeHandler is triggered, even if the node itself is closed. Part of nestedCollectionChangeHandler's function is to dispatch a REMOVE CollectionEvent for all the nodes which were removed by the replacement (which is, all the descendants of the replaced - but closed! - node). Then, since the node that's being replaced is not accessible anymore (because its parent was closed), it's not added to convertedEvent.items. But the next lines assume that the replaced node will be in that array without mistake. Otherwise (as it happens in this bus) it goes into an infinite loop trying to find it.

SOLUTION: instead of looking for the node with an (indefinitely) incrementing index, we're now using Array.indexOf() to locate the node and remove it if it's found.

FLEX-34778 CAUSE: When a node is opened, HierarchicalCollectionView starts to listen to changes to its children collection. And when it's closed, it doesn't stop listening to these CollectionEvents. So when a closed node's child is replaced, nestedCollectionChangeHandler is triggered, even if the node itself is closed. Part of nestedCollectionChangeHandler's function is to dispatch a REMOVE CollectionEvent for all the nodes which were removed by the replacement (which is, all the descendants of the replaced - but closed! - node). Then, since the node that's being replaced is not accessible anymore (because its parent was closed), it's not added to convertedEvent.items. But the next lines assume that the replaced node will be in that array without mistake. Otherwise (as it happens in this bus) it goes into an infinite loop trying to find it.

SOLUTION: instead of looking for the node with an (indefinitely) incrementing index, we're now using Array.indexOf() to locate the node and remove it if it's found.