Finalize, Verify and Commit Attachment Metadata TaskFlow - Full Stack Developer 2026
Never trust “upload finished” from the browser The browser can call finalize even if it uploaded nothing or different bytes. NestJS must verify the object through a privileged Storage API before marking the application row READY.
Verification flow
async complete(id: string, user: AuthenticatedUser) {
const attachment =
await this.attachments.findPendingScoped(id, user.id)if (!attachment) { throw new AttachmentNotFoundException(id) }
const info = await this.storage.info( attachment.bucket, attachment.objectPath, )
if (info.size !== attachment.sizeBytes) { throw new AttachmentUploadMismatchException() }
if (normalizeMime(info.contentType) !== attachment.mimeType) { throw new AttachmentUploadMismatchException() }
return this.attachments.markReady(id, new Date()) }
What info() provides Supabase Storage currently exposes an info(path) API that returns object details such as size, content type and timestamps. It is a useful server-side verification step before committing attachment metadata.
Limits of metadata verification Matching size and declared content type still does not prove the file is harmless. For hostile-file scenarios, add a scanning/quarantine pipeline.
Finalize Verify and Commit Attachment Metadata matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Finalize Verify and Commit Attachment Metadata” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: selected file → validation → upload intent → object storage → metadata/finalize. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Task attachment upload/download/delete workflow using Supabase Storage plus application metadata.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const intent = await api.createUploadIntent({
fileName: file.name,
contentType: file.type,
size: file.size,
});
await storage.uploadToSignedUrl(intent.path, intent.token, file);
await api.finalizeUpload(intent.id);Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Finalize Verify and Commit Attachment Metadata” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Create an upload-intent endpoint that checks authenticated user and target task access before granting upload capability.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Database metadata created before upload succeeds with no cleanup
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.