Rewrite against json_schemer #7
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- same as json_schemer
- Fixes #4
- installs 0 byte cache
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See voxpupuli/json-schema#423 (comment)
I'm mostly opening this for visibility, as I think it makes sense to use a piggy-backed namespace like
json_schemer-fuzzinstead of the one used here. Since this is a rewrite and changing the underlying core dependency I'm not sure if it makes sense to keep the new code under this old namespace.I also have no expectations that this will be merged, though I have already found and fixed several bugs.