[WEB-1972] fix: persist cycle and module Issue properties on page reload in Inbox

[gurusainath]

Problem Statement:

In the inbox, when we preview an issue, the modules and cycles are not rendering in the issue details upon reloading the page.

Solution:

We are retrieving workspace-level issue properties during the page load, which will resolve all persistent issues in the issue preview.

Changes:

1. Inbox page

Plane Issue:

[WEB-1972]

Summary by CodeRabbit

• New Features

  • Enhanced the Workspace Dashboard to dynamically handle different workspaces using the URL context.
  • Integrated workspace-specific issue properties for improved data responsiveness.

• Improvements

  • Improved control flow for fetching workspace issue properties, ensuring timely updates based on user navigation.

[coderabbitai]

Walkthrough

The recent updates to the WorkspaceDashboardPage component enhance its functionality by incorporating the useParams hook for dynamic URL handling. This allows the component to adaptively fetch context-specific workspace issue properties, improving data responsiveness during user navigation. The overall user experience is more fluid and tailored, showcasing a move towards modular and context-aware data handling.

Changes

File Path	Change Summary
web/app/[workspaceSlug]/(projects)/notifications/page.tsx	Enhanced WorkspaceDashboardPage by integrating useParams for dynamic workspace handling and useWorkspaceIssueProperties for context-aware data fetching. Control flow modified for improved responsiveness.

Poem

🐇 In a world of workspaces, hopping around,
New hooks we’ve added, joyfully found.
With each little change, our dashboard's a treat,
Fetching fresh data, oh what a feat!
So leap high and cheer, let the updates ring,
For a smoother experience, let the rabbit sing! 🎶

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9c1c0ed and f7ec321.

Files selected for processing (1)

• web/app/[workspaceSlug]/(projects)/notifications/page.tsx (3 hunks)

Additional comments not posted (3)

web/app/[workspaceSlug]/(projects)/notifications/page.tsx (3)

5-5: Import additions are necessary and correct.

The additions of useParams and useWorkspaceIssueProperties are appropriate for the new functionality.

Also applies to: 18-18

---

21-21: Dynamic URL handling with useParams is appropriate.

The use of useParams to extract workspaceSlug from the URL is correct and necessary for handling different workspaces dynamically.

---

40-41: Fetching workspace issue properties with useWorkspaceIssueProperties is correct.

The integration of useWorkspaceIssueProperties to fetch workspace issue properties based on workspaceSlug is appropriate and enhances the component's responsiveness and context-awareness.