Fix the build (skipping a willDestroyElement test) for canary builds. #179
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The component unit test for
willDestroyElement
is failing due to an issue with Ember 2.9-beta (and canary) where willDestroyElement is triggered after the component has been transitioned to thedestroying
state (and therefore has no element).Will be working on this upstream to fix, but this demonstrates that the remainder of the tests (including component unit tests) are passing on beta and canary.