The schema form facet hierarchy creates a loop since the hierarchy config in facets.facet.* defines that the hierarchy config key is of type facets.facet.[%parent.type]
The becomes an issue when a module like config_views that parses config schemas is enabled since a loop is created.
Enable facets 2.0.1 and config_views on the same site.
Change the schema to define hierarchy type to something that does not create a loop. For example facets.hierarchy.%parent.type]
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | fix_hierarchy_schema-3259836-8.patch | 1.12 KB | herved |
| #2 | facets-config-schema-for-hierarchy-creates-loop-3259836-2.patch | 486 bytes | auth |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
auth commentedAttached is a patch that implements the proposed change
Comment #3
mkalkbrennerComment #4
idebr commentedComment #6
herved commentedThis causes issues with config_inspector which outputs the following when inspecting facet configs:
Seems to relate to #3456858: The LangcodeRequiredIfTranslatableValues constraint can only operate on the root object being validated. but the reporter may also be facing another issue (from another module/schema definition).
If I understand correctly FacetsHierarchy plugins are processors which may have configuration (forms).
So the type should be
plugin.plugin_configuration.facets_hierarchy.[%parent.type]I'll create a merge request for 3.x
Comment #8
herved commentedMR created, here is a static patch which also applies cleanly on 2.0.x
edit: Are tests on 3.0.x currently broken?
Comment #9
herved commented#3459093: Config validation error for facets_processor.* is also related, and also needs to be applied (not released yet)
Comment #13
borisson_Commited and pushed to both 2.x and 3.x