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
{{ message }}
Repository navigation
Commit 199ade8
Browse filesBrowse the repository at this point in the historyBrowse files
fix: say which value failed to parse and why references could not be resolved
- Integer, long and bool scalar errors now include the value and the
reason (not a whole number vs. out of range) and the location of the
field. Schema integer fields used a catch-all that reported every
failure as "The value is out of range"; they now use the same helper.
- A reference whose document cannot be read now reports the underlying
error, and a failed reference is no longer reported twice (once with
the specific reason, then again as "Unable to deserialize reference").
- JsonPointer.Find no longer swallows exceptions. It also returned the
scalar it walked into for pointers such as /info/title/nested instead
of null.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments