Schema for views style displays are missing

New .patch include more missing values in schema.

Yes, please! But make some taxtfields "label" so they can be translated. Using the following now:

# The 'type' should be "label" for short meta tags and "text" for ones which
# could get longer, especially ones which use a textarea field instead of a
# textfield.
views.style.views_bootstrap_dropdown:
  type: views_style
  label: 'Dropdown format'
  mapping:
    button_text:
      type:  label

I added simple labels. Additionally, I added the missing schema for table.

I can confirm this issue. This can be simply reproduced by using config_inspector module:

 	display.default.display_options.style.options.col_xs 	Undefined 	undefined 	Nein 	none 	missing schema 	'col_xs' ist kein unterstützter Schlüssel.
	display.default.display_options.style.options.col_sm 	Undefined 	undefined 	Nein 	none 	missing schema 	'col_sm' ist kein unterstützter Schlüssel.
	display.default.display_options.style.options.col_md 	Undefined 	undefined 	Nein 	col-md-6 	missing schema 	'col_md' ist kein unterstützter Schlüssel.
	display.default.display_options.style.options.col_lg 	Undefined 	undefined 	Nein 	col-lg-4 	missing schema 	'col_lg' ist kein unterstützter Schlüssel.
	display.default.display_options.style.options.col_xl 	Undefined 	undefined 	Nein 	none

Affected config example:

style:
        type: views_bootstrap_grid
        options:
          row_class: ''
          default_row_class: true
          uses_fields: false
          col_xs: none
          col_sm: none
          col_md: col-md-6
          col_lg: col-lg-4
          col_xl: none

Some of these options are never actually used?

"ViewsBootstrapGrid" for example defines loads of options in "defineOptions" but, basically, all of them are not even in use...

Defining these to override core Grid options (like "col_class_default" or "col_class_custom") would make sense if we extend "Drupal\views\Plugin\views\style\Grid", but the "ViewsBootstrapGrid" class is extending "StylePluginBase" instead. So there seems to be no way, to actually change these options, since no UI is provided? Or am I missing something here?

Alright, that should be it. I adjusted the schema and a few default_values. If we want to be 100% clean, we need to provide update hooks for some views style plugins, to map their values to the new ones, in case they are using the default values. But the maintainers should decide here.

LGTM, but a maintainer or someone else should please take a final look & test and RTBC this.