chore: Add workspace slug to should render setting link method

[Saurabhkmr98]

Description

Add workspace slug to should render setting link method

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• New Features
  • Workspace settings now display tailored options based on your active workspace, enhancing the accuracy of visible settings across mobile, sidebar, and command palette views.
  • These updates ensure you access the most relevant settings for your workspace, providing a more context-aware and streamlined navigation experience.

[coderabbitai]

Walkthrough

The changes update the invocation and signature of the shouldRenderSettingLink function across multiple components. The function now requires both the workspace slug (converted to a string) and the setting key for its logic. The updates are applied in UI components such as mobile header tabs, sidebar, and command palette actions, while the helper file now defines a new type alias and modifies the function signature accordingly. Overall, the control flow remains intact, but the rendering logic is refined to be workspace-dependent.

Changes

File(s)	Change Summary
web/app/[workspaceSlug]/.../(with-sidebar)/mobile-header-tabs.tsx web/app/[workspaceSlug]/.../(with-sidebar)/sidebar.tsx web/core/components/command-palette/actions/workspace-settings-actions.tsx	Updated the invocation of shouldRenderSettingLink to include workspaceSlug.toString() as the first argument along with the setting key, modifying the rendering conditions based on workspace context.
web/ce/helpers/workspace.helper.ts	Introduced a new type alias TRenderSettingsLink and updated the function signature of shouldRenderSettingLink to accept both workspaceSlug (string) and settingKey (string) as parameters.

Sequence Diagram(s)

sequenceDiagram
    participant UI as User Interface
    participant SL as shouldRenderSettingLink
    UI->>SL: Call with (workspaceSlug.toString(), key)
    SL-->>UI: Return boolean value
    alt true
       UI->>UI: Render setting link
    else false
       UI->>UI: Do not render link
    end

Loading

Poem

Hopping through code with a joyful skip,
I’ve added a twist to each setting link tip.
Workspace slugs now lead the way,
Rendering logic fresh like a bright new day.
With a wiggle and a hop, bugs flee in a flip—
A bunny’s delight in every code snippet! 🐇

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a43202 and 782d7cf.

📒 Files selected for processing (1)

• web/ce/helpers/workspace.helper.ts (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

web/ce/helpers/workspace.helper.ts (1)

web/core/store/router.store.ts (1)

• workspaceSlug (69-71)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

🔇 Additional comments (1)

web/ce/helpers/workspace.helper.ts (1)

1-2: LGTM! Type and implementation are now correctly aligned.

The addition of the new type alias TRenderSettingsLink and the updated implementation of shouldRenderSettingLink looks good. The function signature now correctly accepts both the workspace slug and setting key parameters, making it consistent with its type definition. While the function currently always returns true, having the parameters properly defined in the implementation will make it clearer and easier to modify in the future when conditional logic might be needed based on these parameters.

This implementation resolves the previous mismatch that was identified between the type signature and the function implementation.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96c403f and 7a43202.

📒 Files selected for processing (4)

• web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/mobile-header-tabs.tsx (1 hunks)
• web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/sidebar.tsx (1 hunks)
• web/ce/helpers/workspace.helper.ts (1 hunks)
• web/core/components/command-palette/actions/workspace-settings-actions.tsx (1 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (3)

web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/sidebar.tsx (2)

web/ce/helpers/workspace.helper.ts (1)

• shouldRenderSettingLink (2-2)

web/core/store/router.store.ts (1)

• workspaceSlug (69-71)

web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/mobile-header-tabs.tsx (2)

web/ce/helpers/workspace.helper.ts (1)

• shouldRenderSettingLink (2-2)

web/core/store/router.store.ts (1)

• workspaceSlug (69-71)

web/ce/helpers/workspace.helper.ts (1)

web/core/store/router.store.ts (1)

• workspaceSlug (69-71)

🔇 Additional comments (3)

web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/mobile-header-tabs.tsx (1)

23-23: Updated function call to include the workspace slug

The function call now correctly includes workspaceSlug.toString() as the first parameter to match the updated function signature in workspace.helper.ts. This allows the rendering logic to consider the workspace context.

web/app/[workspaceSlug]/(projects)/settings/(with-sidebar)/sidebar.tsx (1)

31-31: Updated function call to include the workspace slug

The function call now correctly includes workspaceSlug.toString() as the first parameter to match the updated function signature in workspace.helper.ts. This allows the rendering logic to consider the workspace context.

web/core/components/command-palette/actions/workspace-settings-actions.tsx (1)

43-43: Updated function call to include the workspace slug

The function call now correctly includes workspaceSlug.toString() as the first parameter to match the updated function signature in workspace.helper.ts. This allows the rendering logic to consider the workspace context.