Add backend for querying refs #414
Draft
+238
−1
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
…ectory; please check this into version control
…k this into version control
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 is my attempt to create backend functions that generalizes across a number of issues and anticipates future requests.
#378
#347
#291
There two different sorts of queries that we need:
querying the documents associated with a user
querying all documents
would be used for a users profile, 2. would be used as a more general search function.
To make things simpler for consumers I use the same interface and techniques for both queries. This may be a bit overkill for something like the user profile right now, but I think the uniformity is nice and could allow for more powerful searches later.
Both queries only show documents that the user who is searching is allowed to see (determined by the user id in the session). This can be easily extended to account for publish documents.
I still need to do more testing and to add tests, but I would like to get some feedback before spending more time on this.