- Issue created by @heddn
- Status changed to Needs review
over 1 year ago 2:48pm 12 September 2023 - Open on Drupal.org →Core: 10.1.x + Environment: PHP 8.1 & MySQL 8last update
over 1 year ago Waiting for branch to pass - First commit to issue fork.
- 🇧🇪Belgium herved
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 :\
- 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
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.
- heddn Nicaragua
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.
- 🇧🇪Belgium herved
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). - Status changed to Needs work
2 months ago 9:44am 28 January 2025 - 🇧🇪Belgium herved
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 - 🇧🇪Belgium herved
MR rebased, static patch attached:
- Deletedviews.area.facets_area
-views.area.facets_summary_area
andviews.filter.facets_summary_filter
should be now in facets_summaryNote 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.