Skip to content

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
wants to merge 39 commits into from
Closed

Adding collection field type documentation #794

wants to merge 39 commits into from

Conversation

Moinax
Copy link

@Moinax Moinax commented Oct 22, 2011

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 ?)

weaverryan and others added 30 commits September 7, 2011 06:49
…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
@stof
Copy link
Member

stof commented Oct 23, 2011

@Moinax Your branch should be based on 2.0 when opening a PR to 2.0

@Moinax
Copy link
Author

Moinax commented Oct 23, 2011

Damn, sorry. I do it again in the right branch this time, sorry. Thanks stof for your feedback.

@Moinax Moinax closed this Oct 23, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants