'property' behaviour is different from 'core' entity type about formbundle HOT 6 CLOSED

I agree that property can be confusing, maybe this can be called identifier ?

This type is hidden by default, you have to set it to visible explicitly by passing hidden to false (see getDefaultOptions).

And it make sense to have it as a text field sometimes, think of an "recipient" field, you could directly type the other user login and the form would select the corresponding user directly using this type

from formbundle.

identifier would be better I think. :)

I see the use case for the current text option and I guess it should be kept. Adding another option for "hidden + visible label containing the info derived from the 'property' option" would be nice I think? It makes it possible to add items + descriptions with a label easily when doing autocomplete + rendering the entity_id type with a label when editing a form?

I currently use entity_id to render a collection of entities that get added / deleted by with javascript/autocomplete.

from formbundle.

@asm89, I understand your use case, and I got almost the same (uploading file and rendering the original file name in a box «something.jpg» while the image id is hidden), but there is two problem then :

• That would assume that JS UI update the property in the same time as the entity id
• That implies doing custom field rendering for this case because we would have two sub-fields (the «label» and the identifier) which would complicate the PR on symfony (I'm not sure of how do this without changing the div_layout.html.twig)

from formbundle.

The first thing you mention is an implication of the fact that you use the 'hidden + label option' and not a problem I think. You probably have the text for the label available anyway because that's usually what the user clicks on in the autocomplete? Updating the value + label won't be a problem. You can still use the current options if they will be kept.

I think it would be ok to enable a label to be rendered in the current 'hidden' type.

from formbundle.

And the «label» should be a text field ?

In this case I need to change the way that the field works, adding two sub-fields (for instance identifier and label); where label should be a text field and identifier an hidden value (so the end-user would just see a single field)

I'm not very happy with this approach, I think this is very specific and the label is part of the JS UI, if you have better idea (or if you want to do a PR on this repo) i'm interested in it

My other problem is that my PR on the official symfony repository was not very discussed by repository contributors and the more feature I'll add the more it will be complicated to argue

from formbundle.

I think one of the usecases of this form type is to use it with JS and autocomplete? So adding the label with a description of the hidden type makes sense I think. The text for the label should be determined in the same way as the entity type does now. With this logic in place you can re-render the form with descriptions for your entities etc.

I'll look into what I can do. I'm not sure if the "core" type rendering would have to be adjusted to render a label next to the hidden field.

I agree with you that there is little feedback on your PR, you can try to put it up for discussion another time and hang around IRC a bit?

from formbundle.