basic retrieval endpoint on collaboration server#17
Draft
Conversation
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.
What does this change?
The functionality is very basic - more of a starting point and a way to see the our edits locally. In production, we may need to add pagination to the results.
How to test
Run locally. Go to https://editorial-collaboration.local.dev-gutools.co.uk/documents (on a browser with auth cookies) to see the list of ids of documents in your local collaboration db .
Pick one of the id's and go to https://editorial-collaboration.local.dev-gutools.co.uk/documents/{id} to see a list of steps and timestamps for that document.
How can we measure success?
Have we considered potential risks?
Safe at this point as not used in production.