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

[FEATURE] generate type registry entry in service blueprint #20355

Merged
merged 1 commit into from
Jan 19, 2023

Conversation

chriskrycho
Copy link
Contributor

We have support for this capability in the types, so the blueprints should make sure that there is a registry entry for each service. We originally left this out because we were unsure of the future of the service registry, but we made Owner.lookup() smart enough to resolve it, and the @service decorator continues to expect it.

Helps unblock #20352.

@chriskrycho chriskrycho added enhancement TypeScript Work on Ember’s types labels Jan 19, 2023
We have support for this capability in the types, so the blueprints
should make sure that there is a registry entry for each service. We
originally left this out because we were unsure of the future of the
service registry, but we made `Owner.lookup()` smart enough to resolve
it, and the `@service` decorator continues to expect it.
@chriskrycho chriskrycho enabled auto-merge January 19, 2023 17:09
@chriskrycho chriskrycho merged commit 999619d into master Jan 19, 2023
@chriskrycho chriskrycho deleted the service-registry branch January 19, 2023 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement TypeScript Work on Ember’s types
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants