-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Clarifying Bundle Best Practices is for *reusable* bundles #4250
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
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,19 @@ | ||
.. index:: | ||
single: Bundle; Best practices | ||
|
||
How to Use best Practices for Structuring Bundles | ||
================================================= | ||
Best Practices for Reusable Bundles | ||
=================================== | ||
|
||
A bundle is a directory that has a well-defined structure and can host anything | ||
from classes to controllers and web resources. Even if bundles are very | ||
flexible, you should follow some best practices if you want to distribute them. | ||
There are 2 types of bundles: | ||
|
||
* Application bundles: only use to build your application; | ||
* Reusable bundle: meant to be shared across many projects. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
|
||
This article is all about how to structure your **reusable bundles** so that | ||
they're easy to configure and extend. Many of these recommendations do not | ||
apply to application bundles because you'll want to keep those as simple | ||
as possible. For application bundles, just follow the practices shown throughout | ||
the book and cookbook. | ||
|
||
.. index:: | ||
pair: Bundle; Naming conventions | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo:
used