Repository navigation
chore: add data access user feature description to docs - #1949
Open
zacharyjhankin wants to merge 2 commits into
Open
zacharyjhankin wants to merge 2 commits into
zacharyjhankin wants to merge 2 commits into
Conversation
This branch has not been deployed
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
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.
I know that this is a lot longer than the other ones, but to be honest the other ones are pretty much worthless to anyone actually reading the documentation. So I think it is a good idea to start the precedent of allowing us to write paragraphs for each feature so people know what they do without needing to read through the code.
Diamond ticket: https://jira.diamond.ac.uk/browse/UAS-14800