You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given an iterable of errors, can we define a useful best_match function that returns the best match of the given errors (i.e. the error that seems to most reasonably represent the validation failure?)
Rough idea:
Weigh how deep path and schema_path go into the instance / schema.
Use __lt__ on _Error ( 🎀 ) and return max(errors). Why? Because we can.
The text was updated successfully, but these errors were encountered:
3481a79 Merge pull request #91 from gelraen/nonanchoredpattern
818553f Update pattern.json
b63c96f Merge pull request #92 from gelraen/escapedref
2f043b0 Update ref.json
1ebe2b4 Add valid instances for escaped ref tests
b117902 Add a test that checks for implicit anchoring
d319afa Merge pull request #90 from bugventure/develop
a2c9de2 Add jsen to the list of validators
6d4adfe Merge pull request #87 from legoktm/protocol-relative
824cb99 Add test case for protocol-relative uri validation
git-subtree-dir: json
git-subtree-split: 3481a793ab6a1042a5973549f735b18f2355fb4e
Given an iterable of errors, can we define a useful
best_match
function that returns the best match of the given errors (i.e. the error that seems to most reasonably represent the validation failure?)Rough idea:
path
andschema_path
go into the instance / schema.__lt__
on_Error
( 🎀 ) and return max(errors). Why? Because we can.The text was updated successfully, but these errors were encountered: