Avoid config form field type "machine_name"

Created on 5 May 2025, 8 days ago

Problem/Motivation

This is a follow-up issue on ๐Ÿ› Token name in RenderElementActionBase cannot be specified as nested token Active and we should consistently avoid the usage of machine_name as a form field type.

Proposed resolution

  • There are 11 other cases where the field type machine_name is being used, most of them allow tokens as well and could run into the same problem. We should replace them all for consistency.
  • Most of those cases support tokens or require a token reference, both of which not being declared in the form field configuration. That should be added.
  • Form field validation: those fields that get the token reference attribute will still be validated. But others won't. We may consider our own validation as a replacement for the machine name validation that we've then lost.
๐Ÿ› Bug report
Status

Active

Version

3.0

Component

Code

Created by

๐Ÿ‡ฉ๐Ÿ‡ชGermany jurgenhaas Gottmadingen

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024