feat: (#1072) React 19 Updates for Calendar, DatePicker and DateRangePicker #1151
+75
−50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request updates the dependencies used in the Calendar, DatePicker and DateRangePicker components so that they are compatible with React 19. Specifically this involved the following steps:
I have created the PR against the main branch as directed in the contribution guidelines. However it might be more appropriate that this goes out with other React 19 changes.
Related issue(s)
[Feature]: React 19 support
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Usage of the basic component is unchanged and will continue to function as it did previously. This is supported by no prop changes in Storybook or test suite.
As the current components passes it props down to the React DayPicker component there is the possibility that users might be passing props down which have changed between React DayPicker versions. These props are still passed but might be subject to deprecation in this release or future releases.
How has this been tested?
Functionality is verified against the current Storybook version for the applicable components. Both to ensure there are no regressions and that the external interface for the component is respected. Automated test suite is executed without any testing changes. Both actions executed on an Apple M1 MacBook Pro running Sequoia 15.1.1.
Screenshots (if appropriate):
The PR fulfils these requirements:
main
branch