Refactor Document Access Feature (Client and ServerSide)

[parwatcodes]

This PR Fixes

• Document Access Feature (Public Links) – Client Side Refactoring #217
• Directory & Naming Overhaul #221
• Hooks & Tanstack Query Integration #222
• Confirm Page & Main Access Flow #223
• VisitorInfoModal, Inline PDF, & Analytics #224 (Inline PDF and Analytics will be done in another PR)

This Pull Request will cover the refactor of document access feature:

• Database tables and Directory naming convention changed as requested.
• Integrated API calls using hooks
• Store user required fields in visitorFields and dynamic display fields in the form
• Support for any additional user meta data needed in a table field visitorMetaData
• Integrate hook to upload document and invalidate query which removed explicit url reload to fetch latest documents once a upload is done
• Add constraint to make sure link alias is unique as per a single user only. The below Query will support adding alias with more and one empty and null values but not any scalar values. We need to create a migration and run this query.

-- DropIndex
DROP INDEX "DocumentLink_createdByUserId_alias_key";

-- This allows multiple NULL aliases,
-- but enforces uniqueness on alias per createdByUserId if alias is not null
CREATE UNIQUE INDEX unique_alias_per_user
ON "DocumentLink"("createdByUserId", "alias")
WHERE alias IS NOT NULL AND alias <> '';

To look the UI Changes please go through this merged PR created by @SepidehShahbazi

Overhauling CreateLink modal and SendingAccordion, and adding React Query

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[SepidehShahbazi]

Great work!
I just wanted to mention that on the document page, we're encountering a server error (500) related to displaying documents in the table. As a result, we can't upload documents, and there's an error associated with that as well.
Also, since the name of the link has been changed to documentLink in the Schema file, it might be better to update the corresponding name like linkId in shared/models/linkModels.ts to match that for consistency in the future.