Define schema configuration for mapping instead of sequence

Created on 15 May 2025, 3 months ago

Problem/Motivation

I know this module is only for 10.3 and up but I had the module installed with 10.2 and ran into an error upgrading once on 10.3 related to the schema configuration. I found this issue to be where the schema is using sequence type incorrectly and type object is not valid. I was going to suggest we change the schema to be valid, which requires some code changes.

Proposed resolution

Add a valid configuration that includes mapping.

Remaining tasks

I've added a patch for review.

User interface changes

API changes

Data model changes

πŸ’¬ Support request
Status

Active

Version

2.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States grgcrlsn321

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

Comments & Activities

  • Issue created by @grgcrlsn321
  • πŸ‡ΊπŸ‡ΈUnited States grgcrlsn321

    I've tested this locally and you need to change the layout_paragraphs_restrictions.settings to follow the mapping schema. The main difference would be replacing something like,

    highlight_stack_components:
    context:
    parent_type: highlight_stack
    components:
    - highlight_box

    With,

    highlight_stack_components:
    context:
    parent_type: highlight_stack
    components:
    highlight_box: { }

    The difference would be replacing `- highlight_box` with `highlight_box: { }`.

    I think we can change configurations like this where `- something` would be replaced with `something: { }`.

    I've attached a patch to test with.

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