Uh oh!
There was an error while loading. Please reload this page.
Deprecation Staging - #649
Conversation
rwjblue
commented
Jul 24, 2020
Thanks for working on this @mehulkar! |
rwjblue
commented
Jul 24, 2020
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. 😸 |
camerondubas
commented
Jul 30, 2020
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! |
rwjblue
commented
Jul 31, 2020
@camerondubas - Yep, thanks for pointing that out! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
rwjblue
commented
Jul 31, 2020
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 |
mehulkar
commented
Jul 31, 2020
🥳 great to hear! Enabled seems good to me too, I've updated the text. |
rwjblue
commented
Aug 7, 2020
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. |
rwjblue
commented
Aug 14, 2020
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