@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!

Uh oh!

[Form] Deprecate "read_only" option #10658

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions