Remove the "format" keyword from schemas before running #118
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
michaelmior
force-pushed
the
remove-format
branch
5 times, most recently
from
3ad6dd0 to
6e5461a
Compare
Supporting "format" is optional in all the schemas we are considering. Since Blaze does not implement "format", it would be unfair to compare against other implementations that are performing check this
michaelmior
force-pushed
the
remove-format
branch
from
6e5461a to
8d4fd34
Compare
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.
Supporting "format" is optional in all the schemas we are considering.
Since Blaze does not implement "format", it would be unfair to compare
against other implementations that are performing check this