Field widget

a contribution is welcome

I created 2 branches:
- 3262762-field-widget that uses third_party_settings
- 3262762-field-widget-plugin that defines a new widget plugin extending options_select.

I think the widget plugin option is way better.
We do not have to deal with hooks and a dedicated widget will not pollute all options_select configs. Using third_party_settings, the slim_select dependency and third_party_settings would be exported for all options_select configs, even when unused, which is very annoying.

Also, can we drop 10.2 support (which is EOL) so we can use attributes and not annotations (included since 10.3, https://www.drupal.org/node/3229001 → )

herved → changed the visibility of the branch 3262762-field-widget to hidden.

Checked and also tested !15, I found no problems, it's perfect.

To me the widget config looked a bit weird when I first saw the exported display config, but actually it also makes sense - the first level "settings" key belongs to Drupal's form widgets, but the second "settings" key is actually a Slim Select (object) constructor property, like here https://slimselectjs.com/settings#openPosition

...
field_tags: 
  type: slim_select
  weight: 3
  region: content
  settings:     
    settings:       
      allowDeselect: true
      closeOnSelect: false
      openPosition: top
  third_party_settings: {  }
...

claudiu.cristea → made their first commit to this issue’s fork.

Thank you!

Automatically closed - issue fixed for 2 weeks with no activity.