[spiral/prototype] Initialize PrototypeRegistry only when registry requires from container #1005
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.
This Pull Request improves the way
Spiral\Prototype\PrototypeRegistry
initializes. Previously, it was initialized upon application bootstrap, even when not in use, leading to inefficient resource consumption. The change introducedSpiral\Prototype\Config\PrototypeConfig
, which serves as a central configuration file for managing bindings. Third-party packages can now easily contribute their own bindings to this configuration via bootloader.The PrototypeRegistry is now created only when first requested from the container and utilizes the bindings defined in PrototypeConfig.