Skip to content
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

[Bug] implicit-injections deprecation #19727

Closed
yratanov opened this issue Aug 25, 2021 · 4 comments
Closed

[Bug] implicit-injections deprecation #19727

yratanov opened this issue Aug 25, 2021 · 4 comments

Comments

@yratanov
Copy link

🐞 Describe the Bug

implicit-injections deprecation is being triggered even if I explicitly define service in parent object

🔬 Minimal Reproduction

Create a route file with @service store;, Create another route and inherit it from the first one. Use this.store. See that deprecation warning is shown.

😕 Actual Behavior

Deprecation warning is shown.

🤔 Expected Behavior

I expect to see no deprecation warnings.

🌍 Environment

  • Ember: 3.27.2
  • Node.js/npm: 14.17.5
  • OS: -
  • Browser: -
@snewcomer
Copy link
Contributor

@yratanov Thank you for laying out the issue here. This seems possible. We could build on this PR to add a test case and fix. 4.0 ultimately removed the ability to implicitly inject. Users could live with this deprecation for as long as they don't upgrade to 4.0. It doesn't break nor is shipped to production but is an annoyance that may leave users needlessly searching for it.

Overall I think the answer is, yes we should fix and backport to 3.27.x. The work probably isn't very intensive. Just laying out some thoughts if somebody wanted to contribute a different opinion.

@locks locks added this to Triaging Apr 15, 2022
@snewcomer
Copy link
Contributor

Just coming back to this issue. While I really appreciate this issue, it seems low priority enough to avoid back porting to 3.28. The fix is probably not very impressive and is not terribly critical for users. What do you think @yratanov? While 4.0 might be a big leap for folks from 3.28, I imagine people are working to get to 4.0 anyways where this deprecation is not present.

@gzurbach
Copy link

I spent the last 30 minutes wondering where this deprecation warning was coming from... now I know 😄

@sandstrom
Copy link
Contributor

I'm doing some issue gardening 🌱🌿 🌷 and came upon this issue.

Closing for this reason:

Just coming back to this issue. While I really appreciate this issue, it seems low priority enough to avoid back porting to 3.28. The fix is probably not very impressive and is not terribly critical for users. What do you think @yratanov?

By closing some old issues we reduce the list of open issues to a more manageable set.

This can still be indexed by google, so people can find it if needed, even if it's closed.

@sandstrom sandstrom closed this as not planned Won't fix, can't repro, duplicate, stale Jun 30, 2023
@github-project-automation github-project-automation bot moved this to Done in Triaging Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants