Convert UI Patterns enums ~2.0 to Drupal Core enum format after ~11.2.0 adoption

Created on 7 July 2025, 20 days ago

Problem/Motivation

In Drupal ~11.2.0

Single-Directory Components with properties that have a restricted set of allowed values (using enum) now can specify human-readable labels for each of those allowed values. Those labels are also translatable using Drupal's user interface translation subsystem, and can provide specific translation context via x-translation-context property. This allows projects using Single-Directory Components (like Experience Builder) to better support translatability.

Enum vales do not have translatable labels Active
🐛 Don't raise exception when an enum value is missing from meta:enum Active

This was in UI Patterns ~2.0, and then moved to Drupal Core ~11.2.0

Proposed resolution

  • Convert all "$ref": "ui-patterns://enum_list" to the new Drupal Core enum format.

Remaining tasks

  • ✅ File an issue about this project
  • ❌ Addition/Change/Update/Fix to this project
  • ❌ Testing to ensure no regression
  • ➖ Automated unit/functional testing coverage
  • ➖ Developer Documentation support on feature change/addition
  • ➖ User Guide Documentation support on feature change/addition
  • ➖ UX/UI designer responsibilities
  • ➖ Accessibility and Readability
  • ❌ Code review from 1 Varbase core team member
  • ❌ Full testing and approval
  • ❌ Credit contributors
  • ❌ Review with the product owner
  • ❌ Update Release Notes and Update Helper on new feature change/addition
  • ❌ Release

Varbase update type

  • ✅ No Update
  • ➖ Optional Update
  • ➖ Forced Update
  • ➖ Forced Update if Unchanged

User interface changes

  • N/A

API changes

  • N/A

Data model changes

  • N/A

Release notes snippet

  • N/A
📌 Task
Status

Active

Version

3.0

Component

Code

Created by

🇯🇴Jordan Rajab Natshah Jordan

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

Comments & Activities

Production build 0.71.5 2024