[BUGFIX beta] Allow deprecated access to registry. #12157
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.
As part of the
ember-registry-container-reform
the registry was moved fromApplication#registry
/ApplicationInstance#registry
to__registry__
, and a new public API was created allowing access to the majority of functions that folks used directly onApplication
orApplicationInstance
instances.We created an alias
container
property forApplicationInstances
, but missed creating the same thing forregistry
which was exposed non-underscored on bothApplication
andApplicationInstance
instances.This adds an alias for all public
registry
methods at their original location and provides a helpful deprecation warning instructing you what to use instead.Also, changes the
ApplicationInstance
Object.defineProperty
calls to be done once on theApplicationInstance
prototype (instead of on each instance).This fixes a regression that was reported in a number of prominent projects: