Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
static service injection analysis
See original GitHub issueA while ago I opened https://github.com/embroider-build/embroider/issues/829 because I didn’t understand why a service was not included in the build while it was explicitly injected in multiple locations. This brought up the discussion of a potential staticServices flag for Embroider, and creating an API for injecting services that is easier to statically analyze. It’s been a while since I’ve closed that issue but I still think it would a good addition so I’m opening this one to track it.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This isn’t strictly an embroider concern. We don’t want embroider to support different API than the official Ember docs show. Ember as a whole needs to adopt a different API for service injection.
Embroider is one motivation, but nicer typescript support is another.
Yes, as long as the unit test also imports and registers the service, the same way the other consumers of the service would.