feat: Intercept incompatible (not UTF-8) text on upload #123
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
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
At the moment, if a user uploads a document that contains text unstructured cannot interpret (not utf-8 format), then the user document upload will fail, they’ll flag it to us, we’ll investigate and provide them with a fixed doc. This should just be integrated in the codebase to remove the necessity of manually fixing it.
Changes proposed in this pull request
Amending the upload view to assess the document pre processing for its compatibility with unstructured and converting it if required.
Guidance to review
Do you agree with the approach? Any improvements to be made?
Relevant links
https://uktrade.atlassian.net/jira/software/projects/REDBOX/boards/558?selectedIssue=REDBOX-609
Things to check