-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle generic validation error #103
Conversation
🦋 Changeset detectedLatest commit: da8a9a8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for codemirror-json-schema ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work!
|
||
export { | ||
jsonSchemaLinter, | ||
JSONValidation, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome, this takes care of another ticket i think
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## [email protected] ### Patch Changes - [#103](#103) [`da7f368`](da7f368) Thanks [@imolorhe](https://github.com/imolorhe)! - Handle generic validation error Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Currently we don't return validation errors when we don't have valid corresponding pointers. However we wouldn't always have valid pointers e.g. if the data isn't a valid JSON object (see #98)
Here I just
pushRoot
in those cases. We can consider adding the default root#
pointer but the effect will be the same (i.e. by default all entries will at least match the root pointer and so will set the range to the root)