This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Add the link to the docs in the composer.json #24
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.
The
support
section of the composer.json allows to provide info about several support channels (see https://getcomposer.org/doc/04-schema.md#support for the full list)As the docs are available online, I'm adding the link here, allowing automated tools to benefit from the info. for instance, Packagist displays a link to the documentation when it knows it (sreenshot is for a different package, as zend-escaper will obviously not have this link yet as the PR is not merged):
I'm not adding the issue tracker here, because composer already adds it automatically for github repositories (when calling the API, it checks whether issues are enabled on the repo, and then injects the link to the issue tracker in the support section if there is none provided). The automated injection is better, as it is updated automatically if you rename the github repo.
If you have extra support channels (IRC, mailing-list, forum, etc...), I will let you improve the metadata further.