[PP-1] Make custom block type config entities fully validatable

Created on 27 September 2023, 9 months ago

Updated 4 January 2024, 6 months ago

Problem/Motivation

Block content type config entities are mostly validatable using the typed config system, but are not quite accurate. The revision key should be a boolean, not an integer, but once that's done, they are nearly fully validatable at the API level. (The only other thing they need, arguably, is for the description field to be nullable, but that is blocked on 📌 Configuration schema & required values: add test coverage for `nullable: true` validation support Fixed .)

Steps to reproduce

Proposed resolution

Add constraints to the description element of block_content.type.* in config schema. Also change the revision element to a boolean.

User interface changes

None.

API changes

None.

Data model changes

None.

Release notes snippet

TBD

✨ Feature request

Status

Closed: duplicate

Version

11.0 🔥

Component

Block content →

Last updated 5 days ago

Maintained by
🇦🇺Australia @acbramley
🇺🇸United States @smustgrave
🇦🇺Australia @larowlan

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.

Configuration schema

validation

Comments & Activities

Issue created by @phenaproxima
Open in Jenkins → Open on Drupal.org →
Environment: PHP 8.2 & MySQL 8
last update 9 months ago
Build Successful
@phenaproxima opened merge request.
Status changed to Postponed 7 months ago8:11am 3 December 2023
Comment 7 months ago →
🇧🇪Belgium borisson_ Mechelen, 🇧🇪
Was looking at the configuration validation issues, and noticed this should actually be marked as postponed, changing status to match the reality.
Status changed to Closed: duplicate 6 months ago11:14pm 4 January 2024
Comment 6 months ago →
🇺🇸United States phenaproxima Massachusetts
This is a duplicate of 📌 Add validation constraints to block_content.type.* Needs work .

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024