We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
composer.json
repositories
local
foo
So given a composer.json like this:
{ "repositories": { "local": { "type": "path", "url": "./packages/*/" }, "foo": { "type": "vcs", "url": "..." } } }
See https://getcomposer.org/doc/04-schema.md#repositories
Note: Order is significant here. When looking for a package, Composer will look from the first to the last repository, and pick the first match.
The text was updated successfully, but these errors were encountered:
@mbrodala
Interesting, I did not know that repositories could be an array or an object.
array
object
Thank you for opening an issue!
Sorry, something went wrong.
ergebnis/json-normalizer
Released as https://github.com/ergebnis/composer-normalize/releases/tag/2.30.1!
Thanks a lot for the fix!
You are welcome, @mbrodala!
localheinz
Successfully merging a pull request may close this issue.
Steps required to reproduce the problem
composer.json
withrepositories
local
repository and another repositorylocal
a name which alphabetically follows the other repository (e.g.local
forlocal
andfoo
for a custom VCS package)So given a
composer.json
like this:Expected Result
repositories
order is left unchanged on normalization (example above:local
stays beforefoo
)Actual Result
repositories
are sorted alphabetically which must not happen (example above:foo
is sorted beforelocal
)See https://getcomposer.org/doc/04-schema.md#repositories
The text was updated successfully, but these errors were encountered: