-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Adding collection field type documentation #794
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
Conversation
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
…ed due to a branch mixup
…refixing Versioned path prefixes are useful for CDN's that do not support cache-busting via query strings. This seemed small enough to add as a tip, although it might be better expanded into a cookbook article (and this tip reduced to a "see cookbook" link). Also added a note about required escaping of percentage signs in the option value.
I decided to gloss over the details of how a single base URL is selected from a collection when generating an asset's path, as the internal behavior of UrlPackage is just that.
Framework templating documentation
Conflicts: reference/configuration/framework.rst
…30a3304 [Cookbook] add article regarding changing target path behaviour
Fix spaces in reference/configuration/framework.rst
… merge related to #714
Conflicts: reference/constraints.rst
fixed parameters.yml old ini references
Conflicts: reference/constraints.rst
@Moinax Your branch should be based on 2.0 when opening a PR to 2.0 |
Damn, sorry. I do it again in the right branch this time, sorry. Thanks stof for your feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi, after this great #sfdaycgn and the conference about "Catching Opportunities with Open Source", I decided to add my first little contribution to the symfony-docs. I added pretty much the same documentation as "Embedding a Single Object" for the "Collection" type.
I saw that someone is already working on "prototype" option documentation, so I didn't get further on this, but I can if you need it.
I would like to add a full example like on http://www.siteduzero.com/tutoriel-3-523899-creer-des-formulaires-avec-symfony2.html#ss_part_2 which is pretty great, but I don't know if I can and where I should put this (In cookbook I guess ?)