[5.1] AppNamespaceDetectorTrait refactoring #8084
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
During package development I got into the situation where I wanted to determine the base application namespace (can be changed with
app:namecommand) in a package service provider (equals "on every request")The only way I've found is
AppNamespaceDetectorTrait(correct me if I'm wrong pls)However loading and parsing composer.json on every request is kinda slow.
That's why I propose to parse the kernel object instead.
microtime()shows it is ~10 times faster on fresh L5 install.In my opinion it's cleaner too.