Several schema definitions in wrong sub-modules

Created on 1 September 2025, about 1 month ago

Problem/Motivation

Follows πŸ› Views filter schema Active .
It looks like the schema definitions for views.area.facets_summary_area and views.filter.facets_summary_filter were committed in facets_exposed_filters module while the plugins are defined in facets_summary and can be used without facets_exposed_filters. So these need to be moved in facets_summary.

Also views.filter.facets_filter should be in facets_exposed_filters where the plugin is defined but is currently in facets.

Steps to reproduce

Is this needed?

Proposed resolution

Move things accordingly.

Remaining tasks

do it

User interface changes

N/A

API changes

N/A

Data model changes

N/A

πŸ› Bug report
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium herved

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @herved
  • Merge request !324Resolve #3544226 "Schema definitions" β†’ (Open) created by herved
  • Pipeline finished with Failed
    about 1 month ago
    Total: 700s
    #587266
  • πŸ‡§πŸ‡ͺBelgium herved

    There is another issue, several processor schemas are not defined/missing after πŸ› Config schema fix Active :
    - hide_active_items_processor
    - hide_1_result_facet
    - list_item
    - show_only_deepest_level_items_processor
    - translate_entity_aggregated_fields
    - uid_to_username_callback

    Should we extend the scope here?

  • Pipeline finished with Failed
    about 1 month ago
    Total: 731s
    #587323
  • πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA

    The demo module requires views_ajax_history β†’ but it's not listed in composer.json so the tests fail.

  • Pipeline finished with Failed
    about 1 month ago
    Total: 667s
    #587965
  • πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA

    It then failed because views_filters_summary was required.

    There are still some actual test failures:

    Drupal\Tests\facets\Unit\FacetSource\FacetSourcePluginManagerTest:

        Facet Source Plugin Manager (Drupal\Tests\facets\Unit\FacetSource\FacetSourcePluginManager)
         ⚠ Construct
         βœ” Get definitions
         ✘ Invalid definitions with only·id
           ┐
           β”œ Error: Unknown named parameter $id
        
           β”΄
         ✘ Invalid definitions with only·display_id
           ┐
           β”œ Error: Unknown named parameter $display_id
        
           β”΄
         ✘ Invalid definitions with only·label
           ┐
           β”œ Error: Unknown named parameter $label
        
           β”΄
         ✘ Invalid definitions with no·label
           ┐
           β”œ Error: Unknown named parameter $id
    

    Drupal\Tests\facets\Kernel\FacetManager\DefaultFacetManagerTest:

        Default Facet Manager (Drupal\Tests\facets\Kernel\FacetManager\DefaultFacetManager)
         ⚠ Get enabled facets
         ⚠ Get facets by facet source id
         ⚠ Alter query cacheability metadata
         ✘ Build cacheability metadata with 0
           ┐
           β”œ Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for facets.facet.mars with the following errors: facets.facet.mars:processor_configs.fpc_build_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_post_query_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_sort_processor.settings missing schema
           β”‚
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Development/ConfigSchemaChecker.php:98
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:206
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:56
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Config.php:232
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:260
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php:487
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:239
           β”‚ /builds/issue/facets-3544226/tests/src/Kernel/FacetManager/DefaultFacetManagerTest.php:215
           β”΄
         ✘ Build cacheability metadata with 1
           ┐
           β”œ Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for facets.facet.mars with the following errors: facets.facet.mars:processor_configs.fpc_build_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_post_query_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_sort_processor.settings missing schema
           β”‚
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Development/ConfigSchemaChecker.php:98
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:206
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:56
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Config.php:232
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:260
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php:487
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:239
           β”‚ /builds/issue/facets-3544226/tests/src/Kernel/FacetManager/DefaultFacetManagerTest.php:215
           β”΄
         ✘ Build cacheability metadata with 2
           ┐
           β”œ Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for facets.facet.mars with the following errors: facets.facet.mars:processor_configs.fpc_build_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_post_query_processor.settings missing schema, facets.facet.mars:processor_configs.fpc_sort_processor.settings missing schema
           β”‚
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Development/ConfigSchemaChecker.php:98
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:206
           β”‚ /builds/issue/facets-3544226/vendor/symfony/event-dispatcher/EventDispatcher.php:56
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Config.php:232
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:260
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Entity/EntityStorageBase.php:487
           β”‚ /builds/issue/facets-3544226/web/core/lib/Drupal/Core/Config/Entity/ConfigEntityStorage.php:239
           β”‚ /builds/issue/facets-3544226/tests/src/Kernel/FacetManager/DefaultFacetManagerTest.php:215
           β”΄
    
  • Pipeline finished with Failed
    about 1 month ago
    Total: 649s
    #588079
  • πŸ‡§πŸ‡ͺBelgium herved

    I didn't dig much further tbh because if I'm not mistaken the report is the same as 3.0.x https://git.drupalcode.org/project/facets/-/pipelines/582244
    So this is probably out of scope here and deserves its own issue?
    Thanks for looking into it.

  • πŸ‡ΊπŸ‡ΈUnited States damienmckenna NH, USA

    The issues in DefaultFacetManagerTest appear to be more missing schema, this time in the facets_processors_collection test module, so is relevant for this issue; I don't know about the other one, I haven't dug into it yet.

  • πŸ‡­πŸ‡ΊHungary mxr576 Hungary
  • πŸ‡­πŸ‡ΊHungary mxr576 Hungary
Production build 0.71.5 2024