-
-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Ember 1.13+ #60
Conversation
LGTM |
Why are all the tests failing? |
Ha, because I leaked ES6, and it happened to work natively in Chrome. |
This cleans up deprecations for use with Ember 1.13+, plus one small private API break (the changed `Resolver.create()` call). The removed tests were all testing container resolution of things that are deprecated. There is still coverage for container resolution of Components, which should be sufficient. The test suite still emits a several deprecations, but they are all coming from Ember Data and will need to get fixed there. I paired with @stefanpenner for this PR.
Fixed, Travis is green. |
equal(component._state, 'inDOM'); | ||
}); | ||
|
||
test('can lookup default Ember.Views in its layout', function() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should replace this one with a {{component}} helper version (not blocking this PR though).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, I will work on that, since I also noticed another incompatibility with the new deprecations.
Compatibility with Ember 1.13+
As suggested by @rwjblue [here](emberjs#60 (comment)).
This cleans up deprecations for use with Ember 1.13+, plus one small
private API break (the changed
Resolver.create()
call).The removed tests were all testing container resolution of things that
are deprecated. There is still coverage for container resolution of
Components, which should be sufficient.
The test suite still emits a several deprecations, but they are all
coming from Ember Data and will need to get fixed there.
I worked on this PR with @stefanpenner.
This PR also supersedes #42, which was ready to go and relevant.