[_] fix: encrypt file names on backend #376
Merged
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.
We have been encrypting the file names on the frontend. Since we migrated the endpoint createFile from drive-server and id are not more used, it is difficult for the frontend team to get the respective id to encrypt the name. Therefore, this endpoint encrypts the file name in the backend.
We are already encrypting files on the backend in the endpoint
fileUuid/meta