-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Should render helper be marked as deprecated? #13583
Comments
It is definitely a legacy from an earlier time. I doubt anyone will argue we want to keep it around. It exists mostly because (1) we could only do so much in the run up to 2.0 and we prioritized shipping over completing the entire wishlist of changes, and (2) the volume of deprecations at that time was already very high and the tooling for managing them wasn't as good as it is today, so we deliberately backed off on deprecations for a while to give everybody time to adapt. Now that we are well into the 2.x series, I am in favor of deprecating |
Using |
I'd be interested in taking on some documentation. I found the deprecation guide for using a model in render here. I'm guessing the render deprecation guide would be about the same, although the render model deprecation doesn't mention using services just a component. It would probably make sense to use a service too. |
@ErikCH or anyone else who wants to champion this, please ping me I'm happy to review and help you move forward :-D |
@mixonic Great! Let me know what I should do going forward? Is it just the change to the deprecation guide? What needs to be updated for the rest of the deprecation? |
@ErikCH the steps are going to be something like:
|
It is done, in 2.11 beta shortly. |
https://github.com/emberjs/ember.js/blob/v2.5.0/packages/ember-routing-htmlbars/lib/keywords/render.js#L16 is not marked as deprecated - I was surprised to learn it even still existed actually. Should it be deprecated at this point?
The text was updated successfully, but these errors were encountered: