Some views schemas are (still) missing, maybe

I think print was supposed to be sprint? :)

@vijaycs85: are you working on this? You put it on the sprint :)

Ehem, I actually think that someone who cares about the config system and should not be named here, forgot to cleanup the exported views ... the dependencies are no longer stored for each plugin type,
but just on the most outer entity level.

1.

not sure which style we used (need plugin_id) to define the views.style.[plugin_id]

Oh well, ignore that, this is the the 'vertical_tabs' style, which is contrib, see the export:

      style:
        type: vertical_tabs
        options:
          row_class: ''
          default_row_class: true
          title: title
          summary: ''
          description: ''

2.

This is for the 'bundle' filter type.

Ehem, I actually think that someone who cares about the config system and should not be named here, forgot to cleanup the exported views ... the dependencies are no longer stored for each plugin type,

What about this?

What every committer would ask is where is the test for the changes as it happened in #2358263: Adding missing configuration schema for views blocks. I think it would be great to do these fixes with tests in mind. In talking to @alexpott before there is little chance fixes like this would get in without some test proof.

Sent it for a retest because we now have a LOT more tests. What is the scope of this issue for fixes? Just the errors mentioned in the summary?

Unfortunately not being actively worked on so removing from sprint.

I started working on a reroll, but many of the changes put into view.filter.schema.yml were already added on other tickets Gábor worked.
How was the original list generated? (I can't seem to access it through that link).
Can you point out examples of tests that are kinda close to the ones that need to be written here?

@sidharrell
I had an existing site using the script in https://gist.github.com/dawehner/59fa62a36175e64d8383

@dawehner: can you rerun that script on the (possibly now updated?) site?

I finally got that script running, thanks @dawehner.
I had a lot of trouble at first because I tried to put it in ~/.drush/ so it wouldn't be tied to a particular install, but the autoloader would not pick up SchemaCheckTrait from there. I finally just put it in a module instead. It didn't generate a list of missing config for me, though. I modded it slightly to produce a list of configs that it's checking (attached file), cause maybe (highly probable) I'm doing something wrong.

@vijaycs85: Are the fixes in the proposed patch still relevant?

We discussed this in the CMI meeting today with @Gábor Hojtsy, @effulgentsia, @alexpott, etc. -- In general, for the tests, we should simply add a very basic stub test that uses the given plugin to expose the fail for the missing schema, and then file a normal followup issue to expand the test coverage for that plugin in Views.

Bring on D8MI sprint for consideration.

Looking at the items listed in the issue summary:

- the dependencies ones looks like data bugs, there should not be dependencies stored on that level? why would views store dependencies on that level?
- the style ones look like a custom views style? which style has a title and a description stored?
- the filter value ones have a few maybe missing, but most of the patch does not apply anymore: views.filter_value.string, views.filter_value.in_operator and views.filter_value.bundle are not defined

Until we figure out what is going on here, I think "Some views schemas are (still) missing, maybe" is the best title for this one.

All righto, thanks!