File Policy, Safe Object Paths and Validation TaskFlow - Full Stack Developer 2026
Client metadata is untrusted • file.name may contain awkward characters or misleading extensions.
• file.type is supplied by the client and can be spoofed.
• Size can be checked client-side for UX but must be enforced again server-side and by the bucket.
Allowlist schema const allowedMimeTypes = z.enum([ "application/pdf", "image/png", "image/jpeg", "text/plain", ])
export const createAttachmentIntentSchema = z.object({ originalName: z.string().trim().min(1).max(255), mimeType: allowedMimeTypes, sizeBytes: z.number().int().positive() .max(20 * 1024 * 1024), })
Do not use original filename as identity const extensionByMime = { "application/pdf": "pdf", "image/png": "png", "image/jpeg": "jpg", "text/plain": "txt", } as const
const objectPath = `workspaces/${workspaceId}` + `/tasks/${taskId}` + `/${attachmentId}.${extensionByMime[mimeType]}`
Security consequence The object path is generated from trusted identifiers and an allowlisted extension. The original filename is stored only as display metadata, eliminating path traversal and collision pressure from user-supplied names.
High-risk file types For executables, macro-enabled Office files, archives or regulated uploads, MIME allowlists are not enough. A stronger design adds quarantine plus malware/content scanning before READY.
File Policy Safe Object Paths and Validation 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 “File Policy Safe Object Paths and Validation” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: untrusted input → runtime schema → validated value → business rule → safe operation. 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 CreateTaskSchema = z.object({
title: z.string().trim().min(1).max(160),
priority: z.enum(["LOW", "MEDIUM", "HIGH"]),
});
const input = CreateTaskSchema.parse(requestBody);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 “File Policy Safe Object Paths and Validation” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Generate time-limited access for private objects and test outsider access denial.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Trusting filename extension as MIME proof
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.