Add detailed JSON format descriptions from nextstrain.org docs #1127
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
taken from nextstrain.org docs - seems like auspice should host these
|
Added a similar commit to nextstrain/nextstrain.org#168 to emphasize that v1 should only be used for backward compatibility |
jameshadfield
approved these changes
May 25, 2020
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.
Description of proposed changes
Moving the detailed file descriptions from the nextstrain.org page into the auspice docs. That way auspice docs host the detailed info on file formats and it can be linked in / injected into nextstrain.org docs as necessary and they don't get out of sync.
Related issue(s)
nextstrain/nextstrain.org#164
nextstrain/nextstrain.org#168
Testing
Tested links work locally with docusaurus.
Thank you for contributing to Nextstrain!