Skip to content

fix(Alert): remove redundant boolean from onDismiss prop type #1539

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

Merged
merged 2 commits into from
Mar 25, 2025

Conversation

SutuSebastian
Copy link
Collaborator

@SutuSebastian SutuSebastian commented Mar 25, 2025

Summary by CodeRabbit

  • Refactor

    • Enhanced alert dismiss behavior by switching from a boolean setting to a function callback, offering improved flexibility in user interactions.
    • Updated alert examples to align with the new dismiss interaction for a more consistent experience.
  • Configuration

    • Modified settings to now require a dark mode specification, ensuring consistent styling options across the platform.

… from stories

- Changed the type of `onDismiss` prop in Alert component from boolean to a function type
- Removed `onDismiss` default values from various Alert stories to align with the updated prop type
@SutuSebastian SutuSebastian added 🐛 bug Something isn't working confirmed This bug was confirmed labels Mar 25, 2025
@SutuSebastian SutuSebastian self-assigned this Mar 25, 2025
Copy link

changeset-bot bot commented Mar 25, 2025

🦋 Changeset detected

Latest commit: bd99e99

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

This PR includes changesets to release 1 package
Name Type
flowbite-react 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 Mar 25, 2025

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

Name Status Preview Comments Updated (UTC)
flowbite-react ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 25, 2025 8:04am
flowbite-react-storybook ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 25, 2025 8:04am

Copy link
Contributor

coderabbitai bot commented Mar 25, 2025

Walkthrough

The changes update the Alert component in the flowbite-react library by modifying the onDismiss prop. Its type is now strictly a function conforming to a button’s click event signature rather than a boolean. Accordingly, default onDismiss values have been removed from several Storybook alert configurations. Additionally, the JSON schema now requires the dark property as part of its required fields.

Changes

Files Change Summary
.changeset/yummy-feet-attend.md
packages/ui/src/components/Alert/Alert.tsx
Updated the onDismiss prop type in the Alert component from `boolean
apps/storybook/src/Alert.stories.tsx Removed default onDismiss: false settings from multiple alert story configurations, keeping the dismiss functionality only where a functional callback is defined.
packages/ui/schema.json Updated the JSON schema required fields by adding "dark", so the property list now includes "components", "dark", "path", "prefix", "rsc", and "tsx".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Alert
    participant onDismissCallback

    User->>Alert: Click dismiss button
    Alert->>onDismissCallback: Invoke onDismiss function
    onDismissCallback-->>Alert: Handle dismiss event
Loading

Suggested reviewers

  • rluders

Poem

I'm a rabbit with a joyful hop,
Code paths now clear, no booleans to stop.
Alerts click with function and style,
Dismissing old defaults all the while.
Dark mode's required in our schema so neat,
Hoppin' through changes—a code treat!

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/ui/src/components/Alert/Alert.tsx

Oops! Something went wrong! :(

ESLint: 8.57.0

ESLint couldn't find the plugin "eslint-plugin-react".

(The package "eslint-plugin-react" was not found when loaded as a Node module from the directory "/packages/ui".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-react@latest --save-dev

The plugin "eslint-plugin-react" was referenced from the config file in "packages/ui/.eslintrc.cjs".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • @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.

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/yummy-feet-attend.md (1)

7-7: Minor grammar fix needed

There's a missing article in this sentence.

- Changed the type of `onDismiss` prop in Alert component from boolean to a function type
+ Changed the type of `onDismiss` prop in the Alert component from boolean to a function type
🧰 Tools
🪛 LanguageTool

[uncategorized] ~7-~7: You might be missing the article “the” here.
Context: ...Changed the type of onDismiss prop in Alert component from boolean to a function ty...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 47bde19 and bd99e99.

📒 Files selected for processing (4)
  • .changeset/yummy-feet-attend.md (1 hunks)
  • apps/storybook/src/Alert.stories.tsx (0 hunks)
  • packages/ui/schema.json (1 hunks)
  • packages/ui/src/components/Alert/Alert.tsx (1 hunks)
💤 Files with no reviewable changes (1)
  • apps/storybook/src/Alert.stories.tsx
🧰 Additional context used
🪛 LanguageTool
.changeset/yummy-feet-attend.md

[uncategorized] ~7-~7: You might be missing the article “the” here.
Context: ...Changed the type of onDismiss prop in Alert component from boolean to a function ty...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🔇 Additional comments (3)
packages/ui/src/components/Alert/Alert.tsx (1)

33-33: Good type improvement for the onDismiss prop

This change improves type safety by ensuring that onDismiss prop can only be a function that matches a button's onClick event handler, which is exactly how it's used in the implementation. This is more precise than the previous boolean | (() => void) type and prevents potential type mismatches.

.changeset/yummy-feet-attend.md (1)

5-8: Clear and concise changeset description

The changeset accurately describes the refactoring of the onDismiss prop and related changes.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~7-~7: You might be missing the article “the” here.
Context: ...Changed the type of onDismiss prop in Alert component from boolean to a function ty...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

packages/ui/schema.json (1)

144-144: Verify intent of adding "dark" to required properties

This change makes the "dark" property mandatory in the schema, which seems unrelated to the PR's focus on fixing the onDismiss prop type. While the property has a default value (true), making it required could potentially affect users who don't explicitly provide this field.

Can you confirm if this change is intentional as part of this PR, or if it should be addressed in a separate PR focused on schema updates?

@SutuSebastian SutuSebastian merged commit 6caecce into main Mar 25, 2025
8 checks passed
@SutuSebastian SutuSebastian deleted the fix/alert/on-dismiss-prop branch March 25, 2025 08:07
@github-actions github-actions bot mentioned this pull request Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working confirmed This bug was confirmed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Alert's onDismiss=true doesn't add a dsmiss button
1 participant