feat: PDF annotations for documents (#40) #54
Reference in New Issue
Block a user
Delete Branch "feat/40-pdf-annotations"
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?
Summary
DocumentAnnotationentity + REST endpoints) and reload on page visitANNOTATE_ALL)ANNOTATE_ALLpermission to the Administrators group via Flyway migrationE2E fixes included
beforeAllhooks in the PDF viewer and annotation test suites now use the Playwrightrequestfixture (direct API calls) instead of UI automation — eliminates 90 s timeout failures in CIAnnotationLayer.svelte:closest('[data-annotation]')replaces directdataset.annotationcheck so delete buttons inside annotation divs fire correctlyDataInitializer: reader test user is created independently of the person-seed guard (was silently skipped when DB already had seed data)dev,e2eSpring profiles so the E2E seed always runs locallyTest plan
npm run test:e2e)./mvnw test)🤖 Generated with Claude Code
When a child element inside an annotation div (e.g. the delete button) was clicked, the AnnotationLayer's pointerdown handler would call setPointerCapture, preventing the child's click event from firing. Using closest('[data-annotation]') instead of checking dataset.annotation on the target directly fixes delete buttons inside annotation elements. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>