There should be a validation error when fields schema is invalid

Comments

nginex created an issue. See original summary.

nginex’s picture

Issue summary: View changes
mostepaniukvm’s picture

Assigned: Unassigned » mostepaniukvm
Status: Active » Needs work
mostepaniukvm’s picture

Assigned: mostepaniukvm » Unassigned
Status: Needs work » Needs review
StatusFileSize
new2.27 KB

Implemented validation for YAML value. But I didn't create a constraint plugin because we are not able to use it easily and clearly like in the case of a content entity.
Let me know if you already did something similar and have an idea of how to implement it in a better way.

  • nginex committed 965e31e on 8.x-1.x authored by mostepaniukvm
    Issue #3108989 by mostepaniukvm, nginex: Add constraint to fields_schema...
nginex’s picture

Status: Needs review » Fixed

Looks good

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.