-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
form collection label not correct ? #6607
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
Comments
@HeahDude Would you mind having a look here? |
Hi @flip111, it seems what you're experiencing with the label is expected. In a collection type all sub types (including the prototype) use the same 'entry_options' => array(
'label' => false,
// ...
), When not set as above, the default label used by the prototype is the You could also used |
This shows up as the label for the CollectionType itself, seems like a bug then that the Entry label would affect the CollectionType label ?? For symfony i would suggest making the default label For symfony-docs i would suggest making a change in the javascript part that also does something with the label. Because right now when you just follow the docs you see this var newForm = prototype.replace(/__name__/g, index); The part you are pointing to says: |
We cannot change the entry prototype default label as it would be a major BC break.
I agree that some changes should be made on that part of the docs though, but I don' t see no bug here. |
The comment on the bug is a mistake on my part. So you suggest to replace |
|
Fixes this symfony#6607 in 2.7 branch
Fixes this symfony#6607 in 2.8 branch. See also symfony#8280
Uh oh!
There was an error while loading. Please reload this page.
My form prototype looks something like this
After replacement of
__name__
it looks like:0label__
,1label__
, etc ..i just followed the tutorial with the matching javascript
The text was updated successfully, but these errors were encountered: