[BUGFIX] Try composer autoload of tool installation folder first#268
Merged
simonschaufi merged 1 commit intoandreaswolf:mainfrom Mar 27, 2025
Merged
[BUGFIX] Try composer autoload of tool installation folder first#268simonschaufi merged 1 commit intoandreaswolf:mainfrom
simonschaufi merged 1 commit intoandreaswolf:mainfrom
Conversation
Collaborator
|
Thank you for your contribution. I'll look into the code style issue and then merge it. |
Contributor
Author
Seems like a phpcs update is the reason |
"fractor" as a tool may/should not be installed as a project dependency, but live separately. Hence, the authoritative composer autoload is the one where the tool has been installed to. For legacy reasons the project's autoload information is kept as a fallback. Resolves: andreaswolf#264
b63cc6d to
1f71d03
Compare
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
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.
"fractor" as a tool may/should not be installed as a project dependency, but live separately.
Hence, the authoritative composer autoload is the
one where the tool has been installed to.
For legacy reasons the project's autoload information is kept as a fallback.
Resolves: #264