-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(server): Add support for client-side hashing #2072
Conversation
…/client-side-hashing
…/client-side-hashing
…/client-side-hashing
…/client-side-hashing
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Is it worth doing that in a separate PR, to keep review sizes down? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the scope of this PR has changed a lot over time. It'd be good to update the description to match what's actually being changed here. From what I can tell it is:
- New server endpoint for checking for duplicates via checksum
- No changes to how mobile uploads work
- Removing unique check from web
- Updating checksum column to be non-nullable
If that is all that is changing, we should remove any unrelated changes, like changes to get the objects and locations for user.
server/libs/infra/src/migrations/1679662469076-RemoveChecksumIndex.ts
Outdated
Show resolved
Hide resolved
…/client-side-hashing
The review has been handled but github still shows it as a requested change, I'm closing it
This is the first major PR related to client side hashing. Here, we focus on getting the server-side plumbing done.