feature: introduce composer.json
schema validation
#33
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.
Description
This will verify that the
composer.json
of a project always matches the schema.There are two caveats:
composer.json
if there is one within the projectcomposer.schema.json
to this project to ensure it wont changeThe reason why I've added the schema to this project is, that the schema might change in the future.
Lets take
PSR-0
for example. There is absolutely no reason to support that for like forever.As the
schema.json
on the getcomposer.org website is not versionized, I wanted to take this precaution.I am open to change that to the https://getcomposer.org/schema.json if you think that we don't need this precaution.
This PR relates to #22 but only implements schema validation as suggested by @weierophinney