Skip to content
This repository has been archived by the owner on Mar 22, 2019. It is now read-only.

Commit

Permalink
Merge pull request #3099 from emberjs/locks-patch-3
Browse files Browse the repository at this point in the history
Add upcoming deprecation of targetObject
  • Loading branch information
Jen Weber committed Feb 18, 2018
2 parents cb358de + 36d892a commit 99a3907
Showing 1 changed file with 12 additions and 5 deletions.
17 changes: 12 additions & 5 deletions source/deprecations/v2.x.html.md
Expand Up @@ -1090,15 +1090,22 @@ export default Controller {
}
```
#### Ember 2 Legacy
### Deprecations Added in 2.18
#### `targetObject`
##### until: 3.5.0
##### id: ember-runtime.using-targetObject
The `targetObject` property on `Component` was intended as a "write-only API", meaning that the user was supposed to define their own if they desired, but not read the default one. It was never intended for `this.get('targetObject')` to be used, so it is now deprecated. The recommendation is to use `target` instead.
### Ember 2 Legacy
Ember provides [ember-2-legacy](https://github.com/emberjs/ember-2-legacy) which is an addon to help
app with deprecations during the transition from the 2.x series to 3.x. This addon provides app owners more
time to upgrade off of the deprecations slated for removal in 3.0.0 and depcouples that work from
time to upgrade off of the deprecations slated for removal in 3.0.0 and decouples that work from
upgrading to the 3.x series.
This addon will be supported until 3.4 at which point it will be deprecated.
Once you have removed all deprecations, you can remove the addon with the command:
`npm uninstall ember-2-legacy`
Once you have removed all deprecations, you can remove the addon with the `npm uninstall ember-2-legacy` command.

0 comments on commit 99a3907

Please sign in to comment.