Hello @webmozart I want to start contribuiting in symfony, and i want to get some easy pick. I read the option read_only must be deprectated, but i don't know how to start in this issue. Can you give me some help or some ideas. Thanks for all.

@Hades87 as you can see in the references above your comment, someone already opened a PR about this: #10676

So well, let's find a simple starter issue you can work on.......
I must admit, it was quick a long search to find a simple issue to work on, but I think I've found one for you: #7832 It's about renaming options. This basically means doing 2 things:

• Find all usages of the options you have to rename and replace them with a new name
• Readd this line: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/Extension/Core/Type/FormType.php#L197 (so you end up with both the new and the old option name) and create make the default value of the new option be based on the value of the old option (read about it in the docs). That way, peopling using that application don't have to revisit their code to update the name. That's what we call Backwards Compatibility. It would be nice if you add a comment to this option that it is deprecated and that they need to use the new name.
• Also make sure you add the changes (about deprecating option X in favor of option Y) in the CHANGELOG file, located in the Form component root.

If you have any questions, feel free to ask them in that particular issue, on IRC (#symfony), etc.

Good luck coding!

Thanks for your help @wouterj i take the issue and ask something in the correspondent thread.

-read only still serves its purpose when disabled option is not applicable.

I had this problem when a disabled field failed validation but still passes the containing form as valid. This was not the behavior in pre 2.5 api where even disabled field invalidates the form. Although I find this new behavior the expected one.

but i agree that it should be an attr instead

@webmozart Is there the posibility to have a field readonly / disabled with validation on the field but not altering the model data?

A use case can be that only some have the permission to modify a field which is necessary to process but someone else is then processing the next step after this required field has been submitted.