This repository was archived by the owner on Nov 2, 2023. It is now read-only.
Update hyper-schema section and make it more prominent #196
Conversation
This file contains hidden or 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
Make a _data YAML file for it (sadly Jekyll insists on .yml) and move it up directly under validation.
It looked odd as a top level section either after Hyper-Schema (too far from the validators) or before (which made benchmarks seem more important than hyper-schema, which also isn't right)
philsturgeon
approved these changes
Mar 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Make a _data YAML file for it (sadly Jekyll insists on .yml)
and move it up directly under validation.
The programming language menu is a bit silly with two entries,
but a.) I'm optimistic, and b.) when I took it out it broke and
I can't be bothered to debug that today.
Make benchmarks a subsection of Validators
It looked odd as a top level section either after Hyper-Schema
(too far from the validators) or before (which made benchmarks
seem more important than hyper-schema, which also isn't right)