- Issue created by @bradjones1
- π§πͺBelgium wim leers Ghent π§πͺπͺπΊ
β¨ Introduce "schematic" normalizers Active is in!
I'm convinced that this issue is totally achievable, at least for fully validatable config entities. IOW, I agree with:
This makes schema generation pretty hard because: where do we get a "definitive" list of properties and their acceptable values? Config may have an associated schema β , but the presence of schema is not strictly enforced. Recent changes in Drupal core allow for schemas to be validated, which unlocks things like PATCHing config entities over an HTTP API.
β¦ and there is a clear way to detect which config entities are fully validatable.
Related: my work on β¨ [PP-2] POST/PATCH config entities via REST for config entity types that support validation Needs work . I think that's pretty much a hard blocker for this, but it is working and awaiting review π