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(alert): mark description optional & revise styles when only children is provided #4447

Merged
merged 3 commits into from
Dec 27, 2024

Conversation

wingkwong
Copy link
Member

@wingkwong wingkwong commented Dec 26, 2024

Closes #4445

📝 Description

description is marked as required (from the earliest design). At some point (around 2 months ago), description is only shown when it is provided based on alert.tsx#L66. Hence, it indicates that it should be optional.

Also, when no title & description are provided, says <Alert>Hello</Alert>, the children position is a bit off. This PR also fixes the styling to make it look more natural (see the screenshots below).

⛳️ Current behavior (updates)

image

🚀 New behavior

image

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

📝 Additional Information

Copy link

linear bot commented Dec 26, 2024

Copy link

changeset-bot bot commented Dec 26, 2024

🦋 Changeset detected

Latest commit: 2b9ffa8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages
Name Type
@nextui-org/alert Patch
@nextui-org/theme Patch
@nextui-org/react Patch
@nextui-org/autocomplete Patch
@nextui-org/checkbox Patch
@nextui-org/date-input Patch
@nextui-org/date-picker Patch
@nextui-org/form Patch
@nextui-org/input-otp Patch
@nextui-org/input Patch
@nextui-org/radio Patch
@nextui-org/select Patch
@nextui-org/table Patch

Not sure what this means? Click here to learn what changesets are.

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

Copy link

vercel bot commented Dec 26, 2024

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

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 26, 2024 2:56am
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 26, 2024 2:56am

@wingkwong wingkwong added this to the v2.6.11 milestone Dec 26, 2024
Copy link
Contributor

coderabbitai bot commented Dec 26, 2024

Walkthrough

The pull request introduces changes to the NextUI Alert component, primarily making the description property optional in the @nextui-org/alert package. This modification allows developers to use the Alert component without explicitly providing a description. Additionally, the changes include updating the theme configuration to center-align the alert's main wrapper content, improving the component's flexibility and visual presentation.

Changes

File Change Summary
.changeset/neat-badgers-beam.md Patch for @nextui-org/alert package, marking description as optional
.changeset/new-cups-tan.md Patch for @nextui-org/theme to address component alignment
packages/components/alert/src/use-alert.ts Changed description from required to optional in Props interface
packages/core/theme/src/components/alert.ts Added justify-center to mainWrapper class for vertical content alignment

Assessment against linked issues

Objective Addressed Explanation
Make description prop optional [#4445]
Maintain React 18 and React 19 compatibility

Possibly related PRs

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


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.

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 (1)
.changeset/new-cups-tan.md (1)

5-5: **Grammar fix suggestion **

Improve subject-verb agreement by changing "children is" to "children are":

-fix the alignment when only alert children is provided
+fix the alignment when only alert children are provided
🧰 Tools
🪛 LanguageTool

[uncategorized] ~5-~5: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... the alignment when only alert children is provided

(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ab9ad9b and 2b9ffa8.

📒 Files selected for processing (4)
  • .changeset/neat-badgers-beam.md (1 hunks)
  • .changeset/new-cups-tan.md (1 hunks)
  • packages/components/alert/src/use-alert.ts (1 hunks)
  • packages/core/theme/src/components/alert.ts (1 hunks)
🧰 Additional context used
🪛 LanguageTool
.changeset/new-cups-tan.md

[uncategorized] ~5-~5: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... the alignment when only alert children is provided

(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)

🔇 Additional comments (4)
packages/components/alert/src/use-alert.ts (2)

22-22: **Description JSDoc update improves clarity **

Marking the description prop as "description of the alert message" is more explicit and aligns well with the new optional design.


24-24: **Optional description broadens usage flexibility **

This change allows consumers to omit the description for minimal alert usage scenarios. Ensure that all usage references gracefully handle the absence of a description.

packages/core/theme/src/components/alert.ts (1)

28-29: **Centering content for a consistent layout **

The addition of justify-center helps align alert content vertically. This improves the styling consistency, especially when only minimal content is passed.

.changeset/neat-badgers-beam.md (1)

1-5: **Changeset reflects optional description **

This patch version is consistent with making the description prop optional, promoting flexibility in using alerts without mandatory descriptions.

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.

Alert component forces me to define description prop (React 19)
2 participants