Current reporting is unable to give a good error message in the case of multiple alternative applicable types or constraints.
If we had a notion of edit distance or match score could we use that to narrow down to the more likely/applicable constraint?
Current reporting is unable to give a good error message in the case of multiple alternative applicable types or constraints.
If we had a notion of edit distance or match score could we use that to narrow down to the more likely/applicable constraint?