fix(date-picker): adding props from calendarProps to the getCalendarProps

[macci001]

Closes #3769

📝 Description

The classNames in the calendarProps does not get applied to the calendar.

⛳️ Current behavior (updates)

So currently, the classNames in calendarProps are not propagated to the Calendar due to which the styling does not get applied.

calendarProps={{
    classNames: {
      grid: 'bg-red-800',
    },
}}

As of now, adding the above prop to the date-picker gives following result (does not apply the mentioned style to the grid i.e. bg-red-800):

🚀 New behavior

The PR propagates the calendarProps's classNames so that styling do get apply to them.

calendarProps={{
    classNames: {
      grid: 'bg-red-800',
    },
}}

After the changes in this PR, adding the above prop to the date-picker gives following result (applies the mentioned styling to the grid i.e. bg-red-800 ):

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

Summary by CodeRabbit

• New Features

  • Enhanced the date picker component for improved styling flexibility by allowing users to apply custom class names more effectively.

• Bug Fixes

  • Resolved issues with class name propagation in the calendar component, ensuring that styles are applied correctly.

[changeset-bot]

🦋 Changeset detected

Latest commit: dbb2763

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

This PR includes changesets to release 2 packages

Name	Type
@nextui-org/date-picker	Patch
@nextui-org/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

[vercel]

Someone is attempting to deploy a commit to the NextUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This update introduces a patch for the @nextui-org/date-picker package, specifically enhancing the getCalendarProps function to ensure that classNames are properly propagated within calendarProps. The changes allow for improved customization of the date picker component, enabling users to apply their own styles more effectively. Additionally, modifications to the useDatePicker function enhance how class names are merged and applied, improving the overall usability of the date picker.

Changes

Files	Change Summary
.changeset/flat-pants-accept.md	Updated getCalendarProps to propagate classNames in calendarProps.

Assessment against linked issues

Objective	Addressed	Explanation
classNames in calendarProps should be applied correctly (3769)	✅

Possibly related PRs

• fix(date-picker): corrected inert value for true condition #3054: Modifies the inert attribute in the DatePicker component, related to property handling.
• feat(date-picker): add support for DatePicker to apply styles to DateInput #3146: Adds support for applying styles to the DateInput in the DatePicker, enhancing customization.
• fix(date-picker): update calendar classNames in useDateRangePicker #3258: Updates calendar classNames in the useDateRangePicker, relevant to class name handling.
• fix(date-picker): resolve width clipping issue on 90/110% zoom #3416: Addresses width clipping issues in the DatePicker, improving usability.
• fix(date-range-picker): calendar-content width as per visible-months #3505: Fixes calendar-content width based on visible months, related to display improvements.

Suggested reviewers

• jrgarciadev

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.changeset/flat-pants-accept.md (1)

1-5: LGTM! Consider enhancing the commit message.

The changeset file correctly identifies the package being updated and the nature of the change. The description accurately summarizes the fix being implemented, which aligns with the PR objectives and the linked issue #3769.

Consider slightly modifying the commit message for improved clarity:

-Fixes getCalendarProps to propagate the classNames in the calendarProps. (#3769)
+Fix getCalendarProps to correctly propagate classNames from calendarProps to Calendar component. (#3769)

This modification more explicitly states what the fix does and its impact, which could be helpful for future reference.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7f2fbe4 and dbb2763.

📒 Files selected for processing (1)

• .changeset/flat-pants-accept.md (1 hunks)