Add radios field and checkboxes field

[dontub]

systopia-reference: 26357

[jensschuppe]

Not sure what types of fields this supports …

• Single Checkbox
• Single Radio Button
• multiple Checkboxes
• multiple Radio Buttons
• single-option Select Field
• multi-value Select Field

[dontub]

Not sure what types of fields this supports …

* Single Checkbox

* Single Radio Button

* multiple Checkboxes

* multiple Radio Buttons

* single-option Select Field

* multi-value Select Field

• \Civi\RemoteTools\Form\FormSpec\Field\RadioField: Single radio button. Shall I rename it to RadioButton?
• \Civi\RemoteTools\Form\FormSpec\Field\CheckboxesField: Multiple Checkboxes.

[jensschuppe]

Drupal calls them Radio, Radios, Checkbox, Checkboxes, and Select (the latter with #multiple attribute for Multi-Value Select) - corresponding to HTML element names, which are input types radio, checkbox and the select field type. CiviRemote seems to be consistently adding Field to the class name, so the naming is ok. I was just wondering why the other field types weren't covered.

[dontub]

\Civi\RemoteTools\Form\FormSpec\Field\CheckboxField and \Civi\RemoteTools\Form\FormSpec\Field\SelectField already exist.

In JSON Forms there are only checkboxes for multiple selects specified: https://jsonforms.io/docs/multiple-choice#multi-select

It would be possible to use a custom option like for the [https://jsonforms.io/docs/multiple-choice#radio-button](single radio) to use a select field for multi selects. Yes, I think it would make sense to implement this. However, for the current use case it's not necessary.

Regarding \Civi\RemoteTools\Form\FormSpec\Field\RadioField I've to correct myself: It is meant to define a single value for a single property via a group of radio buttons. So I think it would be reasonable to rename it to RadiosField. A single radio button makes no sense, anyway (and is also in Drupal only internal).