Skip to content
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

[BUGFIX release] Ensure injected property assertion checks container. #13335

Merged
merged 1 commit into from
Apr 14, 2016

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Apr 14, 2016

During the Ember 2.3.0 cycle, we introduced the getOwner / setOwner concepts and deprecated using the injected .container property on objects. Unfortunately, if you are using an older library to create objects that hasn't been updated to use setOwner you would only have the container specified which causes this injection assertion to be thrown (since getOwner(this) returns undefined).

Specifically, using Ember Data 1.13. with Ember 2.4.5 and having a model with an injected property will trigger an assertion.

During the Ember 2.3.0 cycle, we introduced the `getOwner` / `setOwner`
concepts and deprecated using the injected `.container` property on
objects. Unfortunately, if you are using an older library to create
objects that hasn't been updated to use `setOwner` you would only have
the `container` specified which causes this injection assertion to be
thrown (since `getOwner(this)` returns undefined).

Specifically, using Ember Data 1.13.<latest> with Ember 2.4.5 and having
a model with an injected property will trigger an assertion.
@dgeb dgeb merged commit 265da6d into emberjs:master Apr 14, 2016
@homu homu mentioned this pull request Apr 14, 2016
6 tasks
@dgeb
Copy link
Member

dgeb commented Apr 14, 2016

Nice little fix @rwjblue :shipit:

@rwjblue rwjblue deleted the fix-regression-in-injected-properties branch April 14, 2016 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants