Dónal Murtagh

Sorry for the delay, I didn't see your questions until now. I think I see the reason for the confusion now. I'm actually using [h2database](https://www.h2database.com/html/main.html) rather than [HyperSQL](http://hsqldb.org/). They're both...

> I would suggest not using $validators from the ui-schema Based on the example above, it isn't possible to do this with `$validators`, because the validation function only provides access...

@Anthropic not yet, but it's still very much on my radar. I expect to get to this within the next week or two. Sorry for the delay.

@tivie thanks, that's very useful to know. This should be added to the docs

@Anthropic thanks for your response. I agree that visually highlighting validation errors for non-existent fields is obviously impossible, but equally, I'm uneasy about a model that does not conform to...

> my one problem with 'description' is that the json-schema is used for defining only the data definition and validation In my case I use the field description to provide...

> the best I can offer is to update the documentation to indicate the requirement for now and keep this issue as an enhancement that seems like a reasonable interim...

@Anthropic I can confirm that the following successfully works around this issue ```javascript 'x-schema-form': { titleMap: [ {value: 'married', name: 'Married'}, {value: 'single', name: 'Single / separated / divorced /...

I'll test out the latest alpha with this polyfill. It'll likely have to wait until next week though, as I'm on vacation for 2nd half of this week

I've tested with 7.2.0 and the issue still exists. See [this comment](https://github.com/cypress-io/cypress/issues/15898#issuecomment-827617631) for further details. It looks like this issue may be caused by this unresolved Cypress bug https://github.com/cypress-io/cypress/issues/15898