This repository has been archived by the owner on Nov 21, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6ccff1a
commit 6b4b93b
Showing
1 changed file
with
17 additions
and
2 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,20 @@ | ||
--- | ||
"@medusajs/ui": patch | ||
"@medusajs/ui": minor | ||
--- | ||
|
||
fix(ui): Fix issue that was preventing onChange from firing in DatePicker single mode | ||
fix(ui): 2.2.0 | ||
|
||
# Changelog | ||
|
||
## `@medusajs/ui` | ||
|
||
This minor release contains a few bug fixes and improvements, as well as a new primitive component. | ||
|
||
### Fixes | ||
|
||
- Fixes an issue that was preventing the onChange event from firing for the `DatePicker` component when `showTimePicker` was false. | ||
- Fixes an issue where the `DatePicker` component would fire the onChange event when clicking outside of the component. It now only fires the event when the "Apply" button is clicked. | ||
|
||
### New Components | ||
|
||
- Adds a new `Popover` component. This component is a primitive component that can be used to create popovers. It shares much of the same styling as the `DropdownMenu` component, and can be used as a replacement when building highly customized dropdowns where the `DropdownMenu` component is not flexible enough. |