Problem/Motivation
Config entities require validation for REST support. Add a generic "machine_name" type and validate the value.
Proposed resolution
Add type: machine_name with validation constraints — with both the regex and length overridable to allow non-standard machine name shapes.
Impact as measured by #3324984: Create test that reports % of config entity types (and config schema types) that is validatable's ConfigSchemaValidatabilityTest (and diff before124.txt after124.txt):
- Config entity types
- ⏸️ 0.00% → 0.00% validatable (0 of 30 config types — excludes base types)
- 🆙 24.16% → 31.24% average config type validatability
- 🆙 36.10% → 39.35% validatable property paths (200 → 218 of 554 property paths — this excludes property paths for base types)
- Config types
- 🆙 4.61% → 4.76% validatable (29 → 30 of 629 → 630 config types — excludes base types)
- 🆙 25.95% → 26.40% average config type validatability
- 🆙 36.80% → 37.29% validatable property paths (1392 → 1411 of 3783 → 3784 property paths — this excludes property paths for base types)
Remaining tasks
None.
User interface changes
None.
API changes
API addition: machine_name config schema data type
Data model changes
None.