Views filter schema

I'm expanding the scope to all views plugins if you agree.
Opened MR and here is a static patch for composer.

PS: looks like the pipeline is broken on 3.0.x branch :\

I'm not sure we want to add a config schema for views plugins at this time, core views are not yet validated either yet.

core views are not yet validated either

This doesn't feel true. The whole reason I opened this issue in the first place is due to test coverage failing validation.

I work on 3 drupal sites running core 10.3, all passing config_inspector check, this is one of the remaining issues.
Drupal core is fully compliant AFAIK, and phpunit is configured to fail if such issues are found (in \Drupal\Core\Config\Development\ConfigSchemaChecker).

This no longer applies to 3.x

It looks like the facets_area views plugin was removed in 3.0.0-beta2, commit: https://git.drupalcode.org/project/facets/-/commit/c2f70843a5764450659bb...
And there were many other changes, moving back to needs work

MR rebased, static patch attached:
- Deleted views.area.facets_area
- views.area.facets_summary_area and views.filter.facets_summary_filter should be now in facets_summary

Note that views.filter.facets_filter should now in theory be in facets_exposed_filters but is in facets.
I left it as-is for now.

FYI it might be worth adding test coverage for the facets_demo module as a base to work from for this.

WIP test coverage for the facets_demo module.

Should the views schema definition go in the facets_exposed_filters module?

borisson_ → credited michael.acampora → .

@michael.acampora worked in the related issue on similar things, that issue is now closed as duplicate so crediting here.

Should the views schema definition go in the facets_exposed_filters module?

Good question, I think it should, that makes more sense to me.

#14 & #17, no it should not, those schema definitions should go in the module where the plugin is defined, i.e. facets_summary. These can be used without facets_exposed_filters.
Follow up created here: 🐛 Several schema definitions in wrong sub-modules Active