remove global configuration resolver #1118
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.
Exposing it through Globals can cause a race condition. If something (eg, a contrib module) retrieves the configuration resolver from Globals too early during autoloading, then it causes the rest of the objects from Globals to be initialized. This can happen before all required modules have been registered (depending on autoload->files execution order, which is variable). Instead, create a simple API config resolver which does the basics of what the SDK one does (without all the type checking and validation).