Skip to content

Conversation

@gakshita
Copy link
Collaborator

@gakshita gakshita commented Feb 18, 2025

Description

This PR fixes the home's quickstart widget:

  • If there's atleast 1 project and 2 members then the widget is hidden.
  • The links are shown on the basis of permission

Summary by CodeRabbit

  • New Features
    • Enhanced workspace actions, where options to invite team members and configure workspace now reflect your team role and membership status.
  • Refactor
    • Improved evaluation of workspace member counts and button interactivity, ensuring action items are only clickable when eligible.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 18, 2025

Walkthrough

A new hook, useWorkspace, has been introduced to the home widget component to retrieve workspace data. The component now derives an activeWorkspace and checks for admin privileges via isWorkspaceAdmin. The logic for the "visited_members" flag has been updated to verify that the workspace has at least 2 members, and the call-to-action buttons now respect a disabled state from their configuration. These changes refine workspace permission checks and conditional rendering in the component.

Changes

File Change Summary
web/core/.../empty-states/no-projects.tsx Added the useWorkspace hook to retrieve workspace data; introduced activeWorkspace and isWorkspaceAdmin variables; updated member count logic and CTA button state.

Sequence Diagram(s)

sequenceDiagram
    participant NP as NoProjects Component
    participant WS as useWorkspace Hook
    participant WK as Workspace Data

    NP->>WS: Invoke useWorkspace()
    WS->>WK: Request active workspace information
    WK-->>WS: Return workspace data
    WS-->>NP: Provide activeWorkspace info
    NP->>NP: Determine isWorkspaceAdmin status
    NP->>NP: Check if member count >= 2
    NP->>NP: Render actions with appropriate CTA states (enabled/disabled)
Loading

Possibly related PRs

Suggested labels

🌟improvement, 🌐frontend

Suggested reviewers

  • sriramveeraghanta
  • rahulramesha

Poem

I'm a rabbit hopping by,
Celebrating changes with a twinkle in my eye.
New hooks and checks, a workspace delight,
Admin rights and counts glowing bright.
With each button press and code insight,
I dance in ASCII under the moonlight!
🐇✨


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
🪧 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. (Beta)
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
web/core/components/home/widgets/empty-states/no-projects.tsx (3)

128-128: Consider improving the null safety check readability.

The null safety check is correct but could be more readable.

-return (activeWorkspace?.total_members || 0) >= 2;
+return activeWorkspace?.total_members >= 2 || false;

136-136: Maintain consistency in null safety handling.

For consistency with the earlier suggestion, consider updating the null safety check here as well.

-if (storedValue?.hide || (joinedProjectIds?.length > 0 && (activeWorkspace?.total_members || 0) >= 2)) return null;
+if (storedValue?.hide || (joinedProjectIds?.length > 0 && (activeWorkspace?.total_members >= 2 || false))) return null;

178-205: Consider simplifying the conditional rendering structure.

The nested conditional rendering could be made more readable by extracting the link and button rendering into separate components or functions.

Example approach:

const renderCTA = (item: EmptyStateItem) => {
  if (isStateComplete(item.flag) || item.cta.disabled) return null;
  
  if (item.cta.link) {
    return (
      <Link
        href={item.cta.link}
        onClick={handleLinkClick(item)}
        className="text-custom-primary-100 hover:text-custom-primary-200 text-sm font-medium"
      >
        {t(item.cta.text)}
      </Link>
    );
  }
  
  return (
    <button
      type="button"
      className="text-custom-primary-100 hover:text-custom-primary-200 text-sm font-medium"
      onClick={item.cta.onClick}
    >
      {t(item.cta.text)}
    </button>
  );
};
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 473932a and 7677b26.

📒 Files selected for processing (1)
  • web/core/components/home/widgets/empty-states/no-projects.tsx (9 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Analyze (javascript)
  • GitHub Check: Analyze (python)
🔇 Additional comments (2)
web/core/components/home/widgets/empty-states/no-projects.tsx (2)

15-22: LGTM! Workspace integration looks good.

The addition of workspace context and admin permission checks aligns well with the PR objectives of implementing permission-based access control.

Also applies to: 34-34, 48-48


66-66: LGTM! Permission-based CTA controls look good.

The disabled states for CTAs are properly implemented based on user permissions, which aligns with the PR objective of showing links based on user permissions.

Also applies to: 78-78, 90-90, 119-119

@sriramveeraghanta sriramveeraghanta changed the title Fix home quickstart widget fix: home quick start widget validation Feb 18, 2025
@sriramveeraghanta sriramveeraghanta merged commit cba27c3 into preview Feb 18, 2025
5 of 6 checks passed
@sriramveeraghanta sriramveeraghanta deleted the fix-home-quickstart-widget branch February 18, 2025 07:07
lifeiscontent pushed a commit that referenced this pull request Aug 18, 2025
* fix: Handled workspace switcher closing on click

* fix: home quickstart widget
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants