Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix(user): avatar icon not shown in user, when passed #3370

Conversation

awesome-pro
Copy link
Contributor

@awesome-pro awesome-pro commented Jun 30, 2024

Closes #3369

📝 Description

Added name prop in avatarProps, changed name(of avatarProps) to be same as name(of User)

⛳️ Current behavior (updates)

Screenshot 2024-06-30 at 11 09 10 AM

🚀 New behavior

Screenshot 2024-06-30 at 10 53 07 AM Screenshot 2024-06-30 at 10 55 36 AM

💣 Is this a breaking change (Yes/No):

No

📝 Additional Information

Summary by CodeRabbit

  • New Features

    • Footer now includes "All rights reserved." after the company name.
  • Refactor

    • Modified test cases in User component for more accurate assertions.
  • Chores

    • Updated various layout components to include new ScriptProviders. Removed ScriptProviders from the root layout component.
    • Expanded useUser function to accept a name property.

@awesome-pro awesome-pro requested a review from jrgarciadev as a code owner June 30, 2024 05:42
Copy link

changeset-bot bot commented Jun 30, 2024

⚠️ No Changeset found

Latest commit: 0fc9f53

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jun 30, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 30, 2024 6:01am

Copy link

vercel bot commented Jun 30, 2024

@abhinandan-verma is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Jun 30, 2024

Walkthrough

The changes focus on integrating the ScriptProviders component into specific layouts, enhancing the Footer with an additional text, and refining the User component test and useUser function. These modifications improve component functionality and fix a bug related to avatar handling in the User component.

Changes

Files Change Summaries
apps/docs/app/blog/layout.tsx
apps/docs/app/docs/layout.tsx
apps/docs/app/figma/page.tsx
Added import and usage of ScriptProviders component.
apps/docs/app/layout.tsx Removed import and usage of ScriptProviders component.
apps/docs/components/footer.tsx Added “All rights reserved.” text to the footer.
packages/components/user/__tests__/user.test.tsx Changed test case to use getByText instead of querying container directly for finding the name element.
packages/components/user/src/use-user.ts Added name property to avatarProps in the useUser function, allowing it to accept a string or undefined value for the name.

Assessment against linked issues

Objective (Issue #3369) Addressed Explanation
Correct avatar icon display logic by allowing name to be passed through avatarProps

Tip

Early access features: enabled

We are currently testing the following features in early access:

  • OpenAI gpt-4o model for code reviews and chat: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available.

Note:

  • You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
  • Please join our Discord Community to provide feedback and report issues.
  • OSS projects are always opted into early access features.

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>.
    • 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 Configration 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: 1

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9daef56 and 2280c2a.

Files selected for processing (7)
  • apps/docs/app/blog/layout.tsx (2 hunks)
  • apps/docs/app/docs/layout.tsx (2 hunks)
  • apps/docs/app/figma/page.tsx (2 hunks)
  • apps/docs/app/layout.tsx (2 hunks)
  • apps/docs/components/footer.tsx (1 hunks)
  • packages/components/user/tests/user.test.tsx (1 hunks)
  • packages/components/user/src/use-user.ts (2 hunks)
Files skipped from review due to trivial changes (2)
  • apps/docs/app/layout.tsx
  • apps/docs/components/footer.tsx
Additional comments not posted (4)
apps/docs/app/blog/layout.tsx (1)

3-4: Importing and using ScriptProviders.

The ScriptProviders component is correctly imported and used within the JSX structure.

apps/docs/app/docs/layout.tsx (1)

5-5: Importing and using ScriptProviders.

The ScriptProviders component is correctly imported and used within the JSX structure.

packages/components/user/__tests__/user.test.tsx (1)

22-25: Improving test readability and reliability.

Using getByText instead of querying the container directly improves the readability and reliability of the test.

apps/docs/app/figma/page.tsx (1)

5-5: Importing and using ScriptProviders.

The ScriptProviders component is correctly imported and used within the JSX structure.

packages/components/user/src/use-user.ts Show resolved Hide resolved
Copy link
Member

@wingkwong wingkwong left a comment

Choose a reason for hiding this comment

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

  1. Please include a changeset
  2. Please exclude those unrelated files
  3. The test case "should have the passed name" shouldn't be changed. Instead, you should add the new test case for the avatarProp case.

@@ -31,7 +31,7 @@ interface Props {
* The user avatar props
* @see https://nextui.org/docs/components/avatar
*/
avatarProps?: Partial<AvatarProps>;
avatarProps?: Partial<AvatarProps> & {name?: string | undefined};
Copy link
Member

Choose a reason for hiding this comment

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

name is in AvatarProps already. There's no need to add that again.

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.

[BUG] - avatar icon not shown in User component
2 participants