Make webform blocks (block.webform.block:*) fully validatable so they can be used in Experience Builder

Created on 26 May 2025, 8 days ago

Problem/Motivation

Experience Builder requires block configuration to be fully validatable to be included as a component in its tree. This is what the Component Status debugger tells us about webform blocks:

Similar issues include ๐Ÿ“Œ Make menu blocks (block.settings.system_menu_block:*) fully validatable Active and more to find via the related tags.

Steps to reproduce

N/A

Proposed resolution

Make webform block config fully validatable. Verify with config inspector and the Component Status validator in XB.

Remaining tasks

User interface changes

None.

Introduced terminology

None.

API changes

None.

Data model changes

TBD

Release notes snippet

TBD

๐Ÿ“Œ Task
Status

Active

Version

6.3

Component

Code

Created by

๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary

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

Merge Requests

Comments & Activities

  • Issue created by @Gรกbor Hojtsy
  • ๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary

    Added steps to reproduce with screenshot from config inspector and guidance on where to find compatibility checking in XB.

  • First commit to issue fork.
  • Merge request !632Add machine name constraints โ†’ (Open) created by mandclu
  • ๐Ÿ‡ช๐Ÿ‡ธSpain penyaskito Seville ๐Ÿ’ƒ, Spain ๐Ÿ‡ช๐Ÿ‡ธ, UTC+2 ๐Ÿ‡ช๐Ÿ‡บ

    Looked a bit at this with Gรกbor.

    This will be the first step to make Webforms XB compatible, but not enough. I'd suggest we keep the scope here to make it FullyValidatable.

    The bad news, as this uses a yaml blob in its config, a custom xb transform will be needed for the widget.
    The good news, parts of this aparently was done already in WebformTranslationConfigManager for compatibility with config translations form integration.

  • ๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary

    Added ๐Ÿ“Œ Add xb transform to webform block storage so that it works with Experience Builder Active for that, so we can keep scope there.

  • ๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary
  • Pipeline finished with Failed
    8 days ago
    Total: 7426s
    #506888
  • ๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary

    Thanks for looking into this! Tested the MR. The webform block I created is almost validatable now :) The provider and webform block ID seems to have errors still in config inspector:

    I don't know if this block has all the keys that webform blocks have all the time, but if it does, then solving these two would solve it for all webform blocks :)

    I also looked at the component list in XB and it still says that it is not validateable indeed.

  • Pipeline finished with Failed
    7 days ago
    Total: 413s
    #507509
  • ๐Ÿ‡จ๐Ÿ‡ฆCanada mandclu

    @penyaskito could you point me in the direction of a custom xb transform that has already been implemented?

  • Pipeline finished with Failed
    7 days ago
    Total: 505s
    #507705
Production build 0.71.5 2024