REDBOX 76: Adds File status updates to core-api upload #106
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
gecBurton
approved these changes
Mar 14, 2024
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.
Context
While there was already an upload method in the
core-api, there was no way for the front end to find out whether the file had been ingested or embedded. In the future, we anticipate a polling mechanism that can check on the status of a particular file upload.Changes proposed in this pull request
Filemodel, which will allow the front end to give information to users about the status of their uploadGuidance to review
Do the File statuses make sense? Are the trigger points for updating them in the right place?
Relevant links
https://technologyprogramme.atlassian.net/browse/REDBOX-76
Things to check