Pitfall of a different validation strategy

[abelsiqueira]

I was thinking about the validation and errorMessages and wondered if you have considered the following alternate strategy for getMyErrors.

• getMyErrors should receive a object with optional fields instancePath, schemaPath and params.
• Check against errors array for complete match of present fields.
  • For instance, getMyErrors({ params: { missingProperty: 'title' } }) should get the missing title error.
  • getMyNewErrors({ schemaPath: `#/definitions/${props.type}/pattern` }) should get the identifier error
• Instead of returning a list of errors, return a single match, ideally unique.

This approach appears more straightforward to understand, in my opinion, because it's more direct on what constitutes a match.

Possible pitfalls:

• I assume a single match is sufficient, at least for the fields. The type errors can be ignored because they are usually superseded by pattern errors (I think).
• I assume that every error can be mapped by instancePath, schemaPath and params.
• I am not looking too closely at how the Screen level would work.

[abelsiqueira]

I have created a proof of concept: #517