When saving a twig field in Drupal 11.2+ with development.services (config.schema_checker) we can see the warning when saving a twig field.
Schema errors for ds.field.redacted with the following errors: ds.field.redacted:properties.content 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 the documentation.
When using the media title you get errors:
Schema errors for core.entity_view_display.media.document.teaser with the following errors: core.entity_view_display.media.document.teaser:third_party_settings.ds.fields.media_name.settings 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 the documentation.
Save a twig field or add the media name field to a display
Add schema
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 #3
ericgsmith commentedComposer job failure looks unreleated
Comment #4
ericgsmith commentedComment #5
ericgsmith commentedExpanded the scope to some other warnings I picked up
Comment #6
swentel commentedHmm, for some reason, the build fails and the merge doesn't work, not sure why though (same on #3533907: PHP 8.4 - Implicitly nullable via default value null deprecation), will try to figure out later this week.
Comment #7
swentel commentedmerged in, will trigger a new release in a couple of minutes, thanks!
Comment #9
swentel commented