Conversation
|
@josemarluedke YES! Absolutely I can look at some documentation when we are ready and get that updated. Thanks for taking this on. |
|
@josemarluedke I don't think you should attempt to deprecate Thanks for taking this on, please feel free to bug me for reviews etc as you move along :-D |
|
Note that you can ignore deprecations in tests if there are tests for A deprecation guide and audit can totally happen in parallel with this effort, in fact that is even ideal as the two parts of the work can inform each other. |
|
Yes @mixonic, the goal is just to deprecate I didn't know about the Should I leave the tests around |
c68bc10 to
aa4f9a9
Compare
|
This is read for review. I have added I also checked any mentions in the guides for The deprecation guide PR is here: emberjs/website#2700. It could be expanded further if necessary. |
|
👍 I had started this in #14246, thanks for carrying it closer to the line. There is code in the router specifically for having a toplevel |
aa4f9a9 to
9b608cd
Compare
|
I have updated per @chadhietala request. Add a new runtime deprecation and updated the deprecation guide in the same PR as before (emberjs/website#2700). |
|
Nice work! |
|
@josemarluedke @chadhietala @ErikCH Thanks very much for this work! ❤️ |
|
FYI this seems to have introduced some CI test failures: https://travis-ci.org/emberjs/ember.js/jobs/173976039 update: the fix was simple, hardly worth the comment - #14588 |
This implements #13583.
Here is the TODO list from @mixonic.
I'm happy to work in the other items as well, but I'm not sure what to do with the current tests we have. Note that we have quite a few tests around
render intofrom a route e.g. https://github.com/emberjs/ember.js/blob/master/packages/ember/tests/routing/basic_test.js#L1813Also, there are several test failures because of the deprecation. Would love to get some guidance on how to update these tests and migrate the render into tests.
@ErikCH any change you still are interested in taking on some documentation?