First commit of cli docs for data setup #374
Open
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
* tmp commit * tmp commit * tmp commit * For Garrett * Use correct model for widget * work in progress... * end of week commit * work on sequence textarea * tmp commit * only refresh issue remains * Make styling more consistent * Split ApolloFeatureDetails into multiple components * Make widget show feature after reload * Fetch sequence if needed for feature * Move Sequence into its own component * Make a number field that only submits on commit * Remove "save" button on attributes * Update radio buttons --------- Co-authored-by: Garrett Stevens <[email protected]>
This reverts commit 04fed09.
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.
First pass at addressing issue #373 with respect to cli usage for data set setup.
It assumes Apollo is up and running but with nothing in it. So the docs start by setting up a user account. Then it describes how to add data except evidence tracks. It doesn't cover how to edit features or query the database (I guess that would be a separate document?). See if this goes in the right direction...!