[VS-NfD] Warn or block when attaching files to classified pages #213
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#213
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan reference:
20-massnahmenplan.md-> P1-2ADR: ADR 0022
Effort: S (1 AT)
Depends on: #204
Context
Uploading to a classified page is the moment a user needs to be told what
they are doing — the file inherits a classification it cannot itself
carry (#212).
Current state
apps/api/src/files/files.service.tswith pond and pagescoping; no classification-aware behaviour exists (the field arrives with
#204).
Acceptance criteria
consequence, in de and en.
documented default.
server-side (not only in the UI) when enabled.
Out of scope
Scanning file contents, and MIME/extension policy (already
upload.allowedExtensions/upload.svgPolicy).Done in PR #272 (commit
868b79c, CI run 561 green, fast-forward merged on Stefan's standing merge instruction).Evidence: