Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Minor changes throughout Best Practices for Reusable Bundles #7118

New issue

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

Closed
wants to merge 9 commits into from
Prev Previous commit
Next Next commit
Better explain the purpose of the "license" Composer metadata
  • Loading branch information
javiereguiluz authored Feb 14, 2017
commit 73d2d7cef93e3a268b641b76d0d8df1d8caa8057
4 changes: 2 additions & 2 deletions 4 bundles/best_practices.rst
Original file line number Diff line number Diff line change
Expand Up @@ -404,8 +404,7 @@ The ``composer.json`` file should include at least the following metadata:
Use the ``symfony-bundle`` value.

``license``
``MIT`` is the preferred license for Symfony bundles, but you can use any
license.
a string (or array of strings) with a `valid license identifier`_, such as ``MIT``.

``autoload``
This information is used by Symfony to load the classes of the bundle. The
Expand All @@ -426,3 +425,4 @@ Learn more
.. _`Semantic Versioning Standard`: http://semver.org/
.. _`Packagist`: https://packagist.org/
.. _`choose any license`: http://choosealicense.com/
.. _`valid license identifier`: https://spdx.org/licenses/
Morty Proxy This is a proxified and sanitized view of the page, visit original site.