-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Deprecation Staging #649
Deprecation Staging #649
Conversation
Thanks for working on this @mehulkar! |
Just FYI we discussed this at today's core team meeting. Nothing really to report (I don't think most folks have had a chance to review yet), but folks were excited about the progress. 😸 |
Nice! I don't have much to add here, although I think this is a nice progression of the deprecation system. Could the rendered link be added to the PR description? Thanks! |
@camerondubas - Yep, thanks for pointing that out! |
We chatted about this today in the core team meeting. The team is very happy with the overall design and we are eager to move forward. The one area that was still a bit of a concern was around the stage names. We are pretty happy with |
🥳 great to hear! Enabled seems good to me too, I've updated the text. |
Thanks for updating that @mehulkar! We discussed this in the most recent core team meeting, and have decided to move this into final comment period. |
Chatted about this in the core team meeting today, we are still super happy with the direction forward and are ready to land this one! |
This implements the first stage of the Deprecation Staging RFC emberjs/rfcs#649 This commit also: - deprecates the usage of deprecate() function without passing these options - Updates all the usages of deprecate() in the repo to pass these options.
Thanks for @pzuraq,@rwjblue, @wycats, and the rest of the strike team for fleshing out these ideas and letting me play scribe!
rendered