- Issue created by @effulgentsia
- πΊπΈUnited States effulgentsia
Postponing this on π Confirm Semi-coupled form elements can work with autocomplete Active
- Status changed to Active
2 days ago 11:25pm 30 March 2025 - π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
π Allow 6.x version of justinrainbow/json-schema Active is going to be needed here because it uses filter_var to validate URLs and that means
entity:node/3
doesn't validate as a valid URI.https://github.com/jsonrainbow/json-schema/pull/800 is what fixes this upstream but it's only in the 6.x branch.
- π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
π ComponentValidator ignores the set validator and creates a new one Active prevents us from being able to do this using the APIs provided by justinrainbow/json-schema
- π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
This is blocked on π Split model values into resolved and raw Active , π "There are no users matching '' error message appears after reloading the editor page Active and π ComponentValidator ignores the set validator and creates a new one Active
Pushed some code that includes a cherry-pick (Squashed) of π Split model values into resolved and raw Active and π "There are no users matching '' error message appears after reloading the editor page Active that is working on the backend if the core patch from π ComponentValidator ignores the set validator and creates a new one Active is applied
On the frontend - current status is the autocomplete value (e.g
Some node title (3)
doesn't validate with ajv as a uri and hence the field is invalid. I have written a transform to translate this to a uri (entity:node/1) but transforms aren't applied until after the field value validates so we might need to revisit that. Started looking at ajv keywords which are a schema extension that adds support for transforms - but these don't work on strings, only on nested data/objects (because the string is passed by value when we call jsonSchemaValidate)