Doc to describe how to use JSON type definitions #716
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
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
henridf
reviewed
May 3, 2020
Co-authored-by: Henri DF <henridf@gmail.com>
henridf
reviewed
May 3, 2020
henridf
approved these changes
May 3, 2020
Co-authored-by: Henri DF <henridf@gmail.com>
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.
This document describes how to use the
types.jsonwe include withzqand how to customize it for unique environments. Once this is approved/merged, I will then write a corresponding article for the Brim wiki that covers the basics of using the type definitions in the app and links to this doc for details.