Please sign in to comment.
bug #3433 [WIP][Reference][Form Types] Update "radio" form type (bicpi)
This PR was merged into the 2.3 branch. Discussion ---------- [WIP][Reference][Form Types] Update "radio" form type | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | 2.3+ | Fixed tickets | #3410 `radio`'s parent is `checkbox`, not `form`. I need some help regarding the task *value option should be removed from this type*: Should it really be removed? It's because I'm able to set it and it is used in the HTML output. I'm retrieving a boolean value only when I access the submitted data via the form framework but I have also access to the raw, custom value via e.g. `$request->request->get('my_checkbox')`. So maybe it should be moved to the `inherited options` instead for the `radio` field? If yes, the wording would need an update for the `value` option and if no, why keep it for the `checkbox` field? Commits ------- 322b21e Update&Outsource "value" option & update references be47b90 Fix parent type doc reference 22b3d0c [Reference][Form Types] Update "radio" form type
- Loading branch information...
Showing with 22 additions and 31 deletions.
|@@ -0,0 +1,12 @@|
|**type**: ``mixed`` **default**: ``1``|
|The value that's actually used as the value for the checkbox or radio button.|
|This does not affect the value that's set on your object.|
|To make a checkbox or radio button checked by default, use the `data`_|