feat(react-datepicker-compat): Add null to value prop and handle controlled cases correctly #28056
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📊 Bundle size report
🤖 This report was generated against 0eae1bc208e0d69febb4bc1e70ab1e2c7c96b623 |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 4bbb936:
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 0eae1bc208e0d69febb4bc1e70ab1e2c7c96b623 (build) |
🕵 fluentuiv9 No visual regressions between this PR and main |
…to datepicker-compat/controlled
…to datepicker-compat/controlled
khmakoto
reviewed
May 31, 2023
...react-components/react-datepicker-compat/stories/DatePicker/DatePickerControlled.stories.tsx
Outdated
Show resolved
Hide resolved
packages/react-components/react-datepicker-compat/src/components/DatePicker/DatePicker.test.tsx
Outdated
Show resolved
Hide resolved
packages/react-components/react-datepicker-compat/src/components/DatePicker/useDatePicker.tsx
Show resolved
Hide resolved
packages/react-components/react-datepicker-compat/src/components/DatePicker/useDatePicker.tsx
Outdated
Show resolved
Hide resolved
packages/react-components/react-datepicker-compat/src/components/DatePicker/useDatePicker.tsx
Outdated
Show resolved
Hide resolved
…pranopillow/fluentui into datepicker-compat/controlled
khmakoto
approved these changes
Jun 5, 2023
marcosmoura
added a commit
to marcosmoura/fluentui
that referenced
this pull request
Jun 13, 2023
* master: applying package updates doc: Remove wrong recommendation from input (microsoft#28168) fix: Outline color now respects OS force colors settings (microsoft#28182) Datepicker onCalendarOpenStateChange prop (microsoft#28136) feat(react-file-type-icons): Add getFileTypeIconAsUrl utility (microsoft#27336) applying package updates [FIX] Updates selection dot and label positioning for ChoiceGroupOption when an Image or Icon is present. (microsoft#28173) chore(react-infobutton): Rename InfoTip to InfoIcon (microsoft#28177) fix(react-datepicker-compat): Make DatePicker Compat stories SSR safe (microsoft#28017) Added `tab` focus mode to the Breadcrumb (microsoft#28046) docs: Add usable documentation (microsoft#28155) applying package updates Fix up rebase code (microsoft#27864) fix: ContextualMenu indexing in sections (microsoft#28127) applying package updates fix: Layer sets focus visible classname for its FocusRectsProvider (microsoft#28157) docs(react-infobutton): Update stories to show better guidance (microsoft#28144) fix(react-avatar): Do not render the image when src prop is undefined (microsoft#28146) feat(react-datepicker-compat): Add null to value prop and handle controlled cases correctly (microsoft#28056)
|
🎉 Handy links: |
Closed
2 tasks
|
🎉 Handy links: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previous Behavior
Currently the controlled vs uncontrolled use cases are handled the same way as in v8. This is an issue since v8 switches between controlled and controlled without warning.
New Behavior
To avoid this issue and continue using the useControllableState hook, the null type was added to the value prop to handle the controlled cases with null.
Related Issue(s)