Conversation
Introduce SHA-256 `content_hash` generation from original upload bytes and persist it for both `documents` and `labeling_documents`, including Prisma schema updates, migration, and DB indexes. Wire the field through backend services/DTOs, add `content_hash` filtering to `GET /api/documents`, and expand tests across document, OCR, and benchmark flows. Update the frontend document list with a new hash column using an interactive truncated/expandable copyable cell, and add docs describing behavior and normalization interplay.
Expanded document search to include `content_hash` (Content ID) alongside title and filename in the backend query logic. Updated API query docs, added a service test for hash-based search filtering, and aligned the frontend by renaming hash labels to “Content ID,” updating search placeholder text, and showing the Content ID column earlier in the table. Documentation was updated to reflect the new search behavior and terminology.
kmandryk
requested review from
NoorChasib,
alex-struk,
antsand and
dbarkowsky
as code owners
July 2, 2026 20:30
Update test fixtures in hitl.service.spec.ts and upload.controller.spec.ts to include the content_hash field in mock document objects.
dbarkowsky
approved these changes
Jul 6, 2026
dbarkowsky
left a comment
Collaborator
There was a problem hiding this comment.
Yep, working as expected. No concerns after review.
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.
Introduce SHA-256
content_hashgeneration from original upload bytes and persist it for bothdocumentsandlabeling_documents, including Prisma schema updates, migration, and DB indexes. Wire the field through backend services/DTOs, addcontent_hashfiltering toGET /api/documents, and expand tests across document, OCR, and benchmark flows. Update the frontend document list with a new hash column using an interactive truncated/expandable copyable cell, and add docs describing behavior and normalization interplay.Summary
AI-1616
Changes
Testing
Checklist
By submitting this pull request, I acknowledge that I have attempted to meet the following: