### Problem `tagify_facets` is the only Tagify submodule without a `config/schema/` directory. `tagify_link` and `tagify_user_list` both ship one; `tagify_facets` ships none. `TagifyWidget::defaultConfiguration()` declares three settings on top of the parent's: | Key | Default | | ---------------- | ----------------------------------------------- | | `match_operator` | `MatchOperator::Contains->value` (`'CONTAINS'`) | | `max_items` | `10` | | `placeholder` | `''` | Facets resolves a facet's `widget.config` through `facet.widget.config.[%parent.type]`. With no `facet.widget.config.tagify` defined anywhere, it falls back to `facet.widget.config.*` → `facet.widget.default_config`, which declares only `show_numbers`. All three Tagify keys are therefore unschema'd, and saving the facet throws under strict config schema checking. Observed on Drupal 11.3 / Facets 3.0 when saving a facet with `max_items` and `placeholder` set: ```text Drupal\Core\Config\Schema\SchemaIncompleteException: Schema errors for facets.facet.tags with the following errors: facets.facet.tags:widget.config.max_items missing schema, facets.facet.tags:widget.config.placeholder missing schema web/core/lib/Drupal/Core/Config/Development/ConfigSchemaChecker.php:98 ``` `match_operator` is absent from that message only because the reproduction set two keys directly. Saving through `buildConfigurationForm()` persists all three, so a UI save reports all three. ### Why CI does not catch it The fixture `modules/tagify_facets/tests/modules/tagify_facets_test/config/install/facets.facet.tags.yml` sets `widget: {type: tagify, config: {show_numbers: true}}` — the one key the Facets fallback schema does cover — and `TagifyWidgetTest` only ever calls `setWidget('tagify', ['show_numbers' => …])`. The existing test therefore passes with strict schema checking enabled and never exercises the module's own settings. ### Steps to reproduce 1. Enable `facets` and `tagify_facets`. 2. Create a facet and set its widget to **Tagify**. 3. Set *Number of results* (`max_items`) and/or *Placeholder*, then save. 4. With `simpletest.settings:strict_config_schema` enabled (the default under PHPUnit), the save throws `SchemaIncompleteException`. Equivalent one-liner: ```shell drush php:eval "\$f = \Drupal::entityTypeManager()->getStorage('facets_facet')->load('tags'); \$f->setWidget('tagify', ['match_operator' => 'CONTAINS', 'max_items' => 3, 'placeholder' => 'Pick one']); \$f->save();" ``` Without strict checking, the save succeeds silently, but the keys remain schema-less and the values are stored untyped. ### Proposed resolution Add `modules/tagify_facets/config/schema/tagify_facets.schema.yml`, extending the Facets default the same way `facet.widget.config.links` does: ```yaml facet.widget.config.tagify: type: facet.widget.default_config label: 'Tagify widget configuration' mapping: match_operator: type: string label: 'Autocomplete matching' max_items: type: integer label: 'Number of results' placeholder: type: label label: 'Placeholder' ``` `match_operator: string` matches `tagify_user_list.schema.yml`, which types the same setting as `string`. ### Remaining tasks * [ ] Confirm the stored type of `max_items`. Its form element is `#type => number`, which returns a string; if the plugin persists `"3"` rather than `3`, `type: integer` trades the missing-schema error for a type-mismatch error and the widget should cast on submit. Facets' own `soft_limit` pairs `#type => number` with `type: integer`, so casting is the expected fix rather than a looser schema type. * [ ] Extend `TagifyWidgetTest` (or the fixture) to set `match_operator`, `max_items`, and `placeholder`, so strict schema checking actually covers them and this cannot regress. * [ ] Port to `1.2.x` — same gap, same fix. ### Related Adjacent but distinct: #3374361 added the `placeholder` setting and #3588932 covers `maxItems` handling in JS; neither adds schema. `js/tagify-widget.js` compares `max_items === '0'` (string), further evidence the stored type is currently unpinned. ### User interface changes None. ### API / data model changes None. Adding schema documents existing keys; no stored value changes shape.