[BUGFIX beta] Types: resolve services with Owner.lookup
#20319
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Integrate the service registry into the
DIRegistry
introduced as part of rationalizing theOwner
types in PR #20271 (94276b5). This allowsOwner.lookup('service:foo')
to resolve aFooService
if one is set up in the@ember/service
module'sRegistry
interface. The preview types already used this mechanic (as of 5658b13), so this just means that when we ship the stable (i.e. built from source) version of@ember/service
, it will continue working.Meta: Shipping this implementation for the lookup was blocked on being able to publish type modules with
declare module
, which was implemented in PR #20316 (9adcd15). We will likely need to rework other parts of the type hierarchy to support publishing from source.