You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Ember v4.1.0, it's possible to use the service export coming from @ember/service.
This feature was suggested in RFC 752 and implemented in PR 19776.
This means that, at some point, we can deprecate inject in favor of service as having two things to accomplish the same thing is redundant. This issue serves as a reminder to implement that deprecation.
The text was updated successfully, but these errors were encountered:
I'm guessing the main thing here is timing? The RFC states that the deprecation should be until v5, but introducing the deprecation too soon might be annoying for addons that want/need to support Ember versions older than v4.1?
I can bring it up at a Framework meeting soon. I don’t think the timing issue should be a big deal: by the time 5.0 comes out 3.28 will no longer be an LTS, and in fact 4.4 will be nearing the end of its LTS.
Since Ember v4.1.0, it's possible to use the
service
export coming from@ember/service
.This feature was suggested in RFC 752 and implemented in PR 19776.
This means that, at some point, we can deprecate
inject
in favor ofservice
as having two things to accomplish the same thing is redundant. This issue serves as a reminder to implement that deprecation.The text was updated successfully, but these errors were encountered: