Introduce GetServiceTrait. #3843
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
demiankatz
added
the
architecture
1 task
xmorave2
approved these changes
Jul 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR introduces a trait with a getter that wraps around
$this->serviceLocator->get()in order to improve type validation in the code. Now, fetching a service from the service locator will be associated with the appropriate type, enabling more accurate IDE typehints and static analysis.This trait can also serve as a marker for classes that currently make direct access to the service locator, since in the long term it would be better to replace many of these retrieval operations with cleaner dependency injection. I expect that this trait will remain useful indefinitely for some of our more complex factories, however!
TODO