-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Properly track deprecations #459
Comments
This should be done after ember-learn/ember-website#119 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@MelSumner now that we decided against doing ember-learn/ember-website#119 do you have any objection to me moving this into the deprecations repo? using the "transfer issue" feature I mean :) |
This issue has been automatically marked stale. If this issue is something that still needs work, please add a comment and it will remain open, otherwise it will close in 7 days. You are welcome to open a new issue if you miss the window. Thanks! |
Issue
Deprecation items should have a link to the RFC that deprecates the item. This helps with transparency and also confirms that the deprecated item listed has relevant information.
To fix
Example
From https://www.emberjs.com/deprecations/v3.x
In the screenshot below,
Getting the @each property
andUse notifyPropertyChange instead of propertyWillChange and propertyDidChange
should each be a link to the RFC that specifies that they should be deprecated.The text was updated successfully, but these errors were encountered: