Missing config schema for custom_stacked field widget

Created on 11 February 2025, 3 months ago

Problem/Motivation

The custom_stacked field widget is not specified in the config schema and thus results in errors in the config inspector.

Example:
'label' is an unknown key because content.field_accordion_item.type is custom_stacked (see config schema type field.widget.settings.*).<br>'wrapper' is an unknown key because content.field_accordion_item.type is custom_stacked (see config schema type field.widget.settings.*).<br>'open' is an unknown key because content.field_accordion_item.type is custom_stacked (see config schema type field.widget.settings.*).

Steps to reproduce

Install config inspector
Add a field as custom field and use the custom_stacked widget
Go to the config inspector overview and look for the entity form where you added the field
See the config is missing

Proposed resolution

Fix the config schema

Remaining tasks

Create MR
Review MR
Merge MR

User interface changes

None.

API changes

None.

Data model changes

Correct data types in schema.

πŸ› Bug report
Status

Active

Version

3.1

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium tim-diels Belgium πŸ‡§πŸ‡ͺ

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @tim-diels
  • πŸ‡§πŸ‡ͺBelgium tim-diels Belgium πŸ‡§πŸ‡ͺ

    I think this is strange behaviour as there is

    field.widget.settings.*:
      type: custom_field_widget_base
    
    custom_field_widget_base:
      type: mapping
      label: 'Custom field widget settings'
      mapping:
        label:
          type: boolean
          label: 'Show field label?'
        wrapper:
          type: string
          label: 'Wrapper'
        open:
          type: boolean
          label: 'Show open by default?'
    

    that would normally should be picked up.

  • Merge request !91Add schema for custom_stacked β†’ (Merged) created by tim-diels
  • πŸ‡§πŸ‡ͺBelgium tim-diels Belgium πŸ‡§πŸ‡ͺ

    Added the schema for cutom_stacked in meanwhile. But not sure if this is the correct solution, but can't find the cause that creates this issue.

  • Pipeline finished with Success
    3 months ago
    Total: 701s
    #421178
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    Hmm... yeah that is weird. Thanks for the patch, i'll just double check later today that i can reproduce the same warning and verify it fixes and I'll happily merge in. Appreciate the help :)

  • Pipeline finished with Skipped
    3 months ago
    #430110
  • πŸ‡ΊπŸ‡ΈUnited States apmsooner

    Weird that I can't even reproduce the error in config inspector but the patch isn't gonna break anything either way so merging it in and call it fixed. Thanks

  • πŸ‡ΊπŸ‡ΈUnited States apmsooner
Production build 0.71.5 2024