[WEB-1886] fix: mutating the total issues count in the archived issues header when we restore or remove issues from archives

[gurusainath]

Problem Statement:

In the Archived issues, when we restore the issue the total issues count is not mutating in the archived issue header

Solution:

When we restore the issues, we update the total issues count in the archived issues header.

Changes:

1. Archived issue header

Plane Issue:

[WEB-1886]

Summary by CodeRabbit

• Improvements
  • Enhanced the logic for counting issues in the Project Archives, leading to more consistent and streamlined behavior.
  • Simplified control flow in the Project Archives header, improving readability and maintainability for future modifications.

[coderabbitai]

Walkthrough

The update to the ProjectArchivesHeader component improves the method of calculating issue counts by replacing complex conditional logic with a streamlined function call to getGroupIssueCount. This change enhances code readability and maintainability, ensuring consistent behavior for counting issues related to archived projects. The simplification of control flow makes the component easier to understand and modify, promoting a more functional programming style.

Changes

Files	Change Summary
web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/archives/header.tsx	Replaced destructured issueFilters from useIssues with getGroupIssueCount, simplifying the calculation of issueCount and enhancing readability.

Poem

🐇 In a code so neat,
Where issues take their seat,
A function's rise, so bright,
Makes counting pure delight!
With logic clear and flow so fine,
Our projects shine—how divine! ✨

---

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 3545d94 and 78a1bf5.

Files selected for processing (1)

• web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/archives/header.tsx (1 hunks)

Additional comments not posted (2)

web/app/[workspaceSlug]/(projects)/projects/(detail)/[projectId]/archives/header.tsx (2)

29-29: LGTM! Simplified issue count calculation.

The use of getGroupIssueCount directly improves code readability and maintainability.

---

35-35: LGTM! Centralized issue counting logic.

The use of getGroupIssueCount centralizes the logic for counting issues, improving maintainability. Ensure that the parameters passed to getGroupIssueCount are correct and cover all intended cases.