This repository has been archived by the owner on Nov 2, 2023. It is now read-only.
Structured validation library information #131
Merged
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
adamvoss
force-pushed
the
structured-library-information
branch
from
ddd7f10 to
6f75293
Compare
adamvoss
force-pushed
the
structured-library-information
branch
from
6f75293 to
8362a1c
Compare
|
Updated to include the latest changes from master. |
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.
This moves the library information from the implementations page into a (semi-)structured format, then generates very nearly the same output.
This makes it far easier to change the layout if anyone were to want to in the future (ex. a table). Another potential use would be to standardize the specification of supported JSON Schema versions or other project attributes.