Document Access Feature (Public Links) – Client Side Refactoring

[mahid797]

Refactor the current /links/[linkId] feature into a clearer, maintainable, and future-proof “Document Access” flow, fully aligned with the new server-side JSON-based visitorFields and potential name/email columns. The refactoring will improve code organization, add Tanstack Query usage for data fetching, and introduce a more flexible approach to collecting visitor data and handling analytics (views/downloads).

Overview

• Migrate from links/[linkId] to documentAccess/[linkId], renaming files and reorganizing the directory.
• Implement a “Confirm” page with disclaimers.
• Create a new main AccessPage.tsx that fetches link details via Tanstack Query.
• Introduce dynamic visitor fields (from JSON) in VisitorInfoModal.tsx.
• Allow inline PDF viewing in a global PDFViewer.tsx.
• Track analytics (e.g., direct access or download events).

Key Note

The server only stores minimal keys or booleans for which visitor fields are requested. Labels or “required” flags do not reside in the DB. The client references src/shared/config/visitorFieldsConfig.ts to render form fields, ensuring any additional columns (like name/email) or dynamic fields remain consistent.

---

Sub-Issues

1. Directory & Naming Overhaul #221
2. Hooks & Tanstack Query Integration #222
3. Confirm Page & Main Access Flow #223
4. VisitorInfoModal, Inline PDF, & Analytics #224

References

• Server-Side Refactoring Issue: Document Access Feature (Public Links) – Server Side Refactoring #216

📄 Note:
It is strongly recommended to read through all related issues (both Server Side and Client Side) before beginning development to ensure a full understanding of the scope, dependencies, and overall feature flow. This will help avoid redundant work and ensure consistency across all components.