Problem/Motivation

Fix config schema

Proposed resolution

Remove the strictSchemaChecking = FALSE in the tests and make them pass.

Remaining tasks

None.

User interface changes

None.

API changes

Route renames.

Data model changes

None.

Comments

giancarlosotelo’s picture

StatusFileSize
new4.91 KB

Tests are green now.

giancarlosotelo’s picture

Status: Active » Needs review
berdir’s picture

+++ b/config/schema/flag.schema.yml
@@ -55,3 +55,53 @@ flag.flag.*:
       label: 'ID of the Link Type plugin'
+    flagTypeConfig:
+      type: mapping
+      label: 'Flag Type Configuration'

Nice.

The problem now is that those two are plugin-based configuration.

So they can be different based on the used link type.

So we need a dynamic schema, based on the value of the plugin, and at least for the flag type, it probably also needs a wildcard as that is automatically exposed for all entity types.

See search_api.schema.yml for an example for the dynamic definition and search_api.datasources.schema.yml for an example of a dynamic wildcard thing.

berdir’s picture

Status: Needs review » Needs work
giancarlosotelo’s picture

Status: Needs work » Needs review
StatusFileSize
new5.76 KB
new3.58 KB

Added a dynamic schema for flag type and link type.

giancarlosotelo’s picture

StatusFileSize
new5.7 KB
new2.22 KB

I delete one 'flag.' string and also works. It is cleaner now.

berdir’s picture

Status: Needs review » Reviewed & tested by the community

Nice!

joachim’s picture

Status: Reviewed & tested by the community » Fixed

Brilliant! This was a major issue with our tests. Thanks for working on it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.