Some elements saved in the module’s configuration object are not defined in the configuration schema. This triggers a warning during config export/import and in other operations that validate schema.
Schema errors for orejime.settings with the following errors:
orejime.settings:request_path missing schema,
orejime.settings:logo missing schema,
orejime.settings:implicit_consent missing schema,
orejime.settings:color missing schema.
These errors mean there is configuration that does not comply with its schema. This is not a fatal error, but it is recommended to fix these issues. For more information on configuration schemas, check out <a href="https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-schemametadata">the documentation</a>.
drush cex). The warning may also appear later during a configuration re-import (drush cim), when enabling another module (e.g., drush en some_module), or when saving configuration again in the back office.
request_pathlogocolorimplicit_consent element from the config form, as it appears to no longer exist / be used.
Active
3.0
Code
I also just noticed that the mapping for name, apps, and weight is missing in the category sequence.
I’m adding a new commit to include this mapping, as well as proper type handling for apps and weight in the config form submit.