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
Reverted the changes about bundle namespaces
  • Loading branch information
javiereguiluz authored Feb 14, 2017
commit 07dd2601a18a22098c3330f02fb39c6ccc44630c
9 changes: 4 additions & 5 deletions 9 bundles/best_practices.rst
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,10 @@ the guides.
Bundle Name
-----------

A bundle name is also a PHP namespace. The namespace must follow the `PSR-0`_
or `PSR-4`_ interoperability standards for PHP namespaces and class names.
The name starts with the vendor name, followed by zero or more category
segments/names, and it ends with the namespace short name which must end
with ``Bundle``.
A bundle is also a PHP namespace. The namespace must follow the `PSR-0`_ or
`PSR-4`_ interoperability standards for PHP namespaces and class names: it starts
with a vendor segment, followed by zero or more category segments, and it ends
with the namespace short name, which must end with ``Bundle``.

A namespace becomes a bundle as soon as you add a bundle class to it. The
bundle class name must follow these simple rules:
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.