-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: only two keyframes currently supported with spring and inertia animations #2596
fix: only two keyframes currently supported with spring and inertia animations #2596
Conversation
🦋 Changeset detectedLatest commit: c24c4d5 The changes in this PR will be included in the next version bump. 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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@wingkwong is attempting to deploy a commit to the NextUI Inc Team on Vercel. A member of the Team first needs to authorize it. |
Important Auto Review SkippedAuto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the WalkthroughThe changes involve updating the Changes
Assessment against linked issues
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yaml
Files selected for processing (13)
- apps/docs/components/sandpack/use-sandpack.ts (2 hunks)
- apps/docs/package.json (1 hunks)
- packages/components/accordion/package.json (1 hunks)
- packages/components/autocomplete/package.json (1 hunks)
- packages/components/dropdown/package.json (1 hunks)
- packages/components/modal/package.json (1 hunks)
- packages/components/popover/package.json (1 hunks)
- packages/components/ripple/package.json (1 hunks)
- packages/components/select/package.json (1 hunks)
- packages/components/tabs/package.json (1 hunks)
- packages/components/tooltip/package.json (1 hunks)
- packages/utilities/framer-transitions/package.json (1 hunks)
- pnpm-lock.yaml (13 hunks)
Additional comments: 15
packages/utilities/framer-transitions/package.json (1)
- 49-49: The update of
framer-motion
to^11.0.22
aligns with the PR objectives. Ensure compatibility with other dependencies is verified, especially those that might interact withframer-motion
.packages/components/ripple/package.json (1)
- 51-51: Update to
framer-motion
version^11.0.22
is consistent with the PR's objectives. Ensure that this update does not introduce compatibility issues with other dependencies within theripple
component.packages/components/dropdown/package.json (1)
- 61-61: The update to
framer-motion
version^11.0.22
is in line with the PR's objectives. Verify compatibility with other dependencies, particularly those related to dropdown functionality.packages/components/tooltip/package.json (1)
- 61-61: Update to
framer-motion
version^11.0.22
aligns with the PR's objectives. Ensure compatibility with other dependencies, especially those related to tooltip functionality.packages/components/popover/package.json (1)
- 66-66: Given the Popover component's direct relevance to the PR's objectives, the update to
framer-motion
version^11.0.22
is particularly important. Ensure thorough compatibility checks with other dependencies, especially those directly involved in the Popover's functionality.packages/components/tabs/package.json (1)
- 62-62: Update to
framer-motion
version^11.0.22
aligns with the PR's objectives. Verify compatibility with other dependencies, particularly those related to tabs functionality.packages/components/modal/package.json (1)
- 68-68: The update to
framer-motion
version^11.0.22
is consistent with the PR's objectives. Ensure compatibility with other dependencies, especially those related to modal functionality.packages/components/accordion/package.json (1)
- 73-73: Update to
framer-motion
version^11.0.22
aligns with the PR's objectives. Verify compatibility with other dependencies, particularly those related to accordion functionality.packages/components/select/package.json (1)
- 69-69: The update of
framer-motion
to11.0.22
is aligned with the PR's objective to address specific animation issues. Ensure thorough testing is conducted to verify that this update does not introduce any breaking changes or incompatibilities with the select component or its dependencies.packages/components/autocomplete/package.json (1)
- 73-73: The update of
framer-motion
to11.0.22
is aligned with the PR's objective to address specific animation issues. Ensure thorough testing is conducted to verify that this update does not introduce any breaking changes or incompatibilities with the autocomplete component or its dependencies.apps/docs/package.json (1)
- 57-57: The update of
framer-motion
to11.0.22
is aligned with the PR's objective to address specific animation issues. Ensure thorough testing is conducted to verify that this update does not introduce any breaking changes or incompatibilities with the docs app or its dependencies.apps/docs/components/sandpack/use-sandpack.ts (1)
- 73-73: The update of
framer-motion
to11.0.22
within theuseSandpack
function is aligned with the PR's objective to address specific animation issues. Ensure thorough testing is conducted to verify that this update does not introduce any breaking changes or incompatibilities with the useSandpack function or its dependencies.pnpm-lock.yaml (3)
- 391-392: The update of
framer-motion
to version11.0.22
with dependencies on[email protected]
and[email protected]
is correctly formatted and aligns with the PR objectives. This change ensures that the specified versions ofreact
andreact-dom
are used alongsideframer-motion
, which is crucial for compatibility and avoiding version conflicts.- 678-679: This hunk also correctly updates
framer-motion
to version11.0.22
and specifies the correct versions ofreact-dom
andreact
. It's important to maintain consistency across all instances whereframer-motion
is used to ensure that the library functions as expected across the entire project.- 16875-16892: The detailed specification for
[email protected]
including its resolution, peer dependencies, and dependencies is correctly updated. This ensures that the correct versions ofreact
andreact-dom
are used as peer dependencies and directly as dependencies, which is essential for the correct functioning offramer-motion
within the project. Markingreact
andreact-dom
as optional peer dependencies provides flexibility, allowing this version offramer-motion
to be used in environments where different versions of React might be in use, though this project specifies18.2.0
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 0
Configuration used: .coderabbit.yaml
Files selected for processing (1)
- .changeset/famous-jobs-wonder.md (1 hunks)
Additional comments: 2
.changeset/famous-jobs-wonder.md (2)
- 14-14: Consider revising the description for enhanced clarity and formality. Additionally, ensure there are no spelling errors.
- 2-11: The version patches for the components and utilities are correctly annotated and align with the PR objectives.
cool, just encountered this problem. |
* refactor(input): input ref test (#2613) * refactor(input): remove duplicate test * refactor(input): remove unncessary waitFor * fix(radio): isRequired & missing warning message in Form (#2597) * fix(radio): avoid overriding required props * fix(radio): merge with domRef * feat(changeset): fixed missing required props and validationMessage * fix(radio): unnecessary mergeRefs * Calendar component 📅 (#2456) * feat(calendar): initial structure * feat(calendar): calendar structure completed, styles in progress * chore(calendar): dark colors adjusted * feat(calendar): styles improved, variants added, animations added with framer motion * chore(calendar): animation changed, shadow improved * chore(calendar): disableAnimation support added as well as weekDays format * feat(calendar): more stories added * chore(calendar): refactor calendar cell styling * feat(calendar): create calendar function added to the root provider * feat(calendar): invalid state and error message added * feat(calendar): calendar picker added, provider modified * feat(root): object.values deps replaced by new func, intersection hoook added, types version unified * feat(calendar): calendar pickers in progress * feat(calendar): calendar pickers added * fix(calendar): year label formatting * chore(calendar): add layout parameter to Calendar stories * feat(calendar): pickers completed, context added * feat(calendar): visibleMonths supported, warnings fixed, tests added * chore(root): changeset * chore(calendar): add topContent and bottomContent props to calendar * feat(calendar): add @nextui-org/radio package and update calendar component * refactor: assigned type(DateValue) to focusedDate(ControlledFocusedVaue) (#2637) Co-authored-by: shrinidhi.upadhyaya <[email protected]> * Range Calendar 📆 (#2634) * feat(calendar): range calendar added, calendar and context adapted * feat(calendar): range calendar stories added * chore(calendar): range calendar tests added * fix(calendar): update calendar styles to adjust to dynamic width * Date Input 🗓️ (#2641) * feat(date-picker): date field component initialized * chore(date-picker): date field renamed to date-input * feat(date-picker): date input completed * chore(date-input): commented code removed * feat(avatar): support slots in AvatarGroup (#2669) * feat: rename newPost to new (#2665) * fix(avatar): spread getAvatarGroupCountProps in avatar count * feat(avatar): support slots in avatarGroup * feat(avatar): support classNames and add getAvatarGroupCountProps * feat(docs): add classNames to avatar group * feat(avatar): add CustomSlots in avatar group * feat(changeset): support slots in avatar group --------- Co-authored-by: winches <[email protected]> * Date Picker Component 🗓️ (#2652) * feat(date-picker): first iteration * chore(date-picker): update date-picker README.md with improved description * feat(date-picker): code organized, integration done * fix(date-picker): min and max value + styles * fix(date-picker): popover offset adn calendar styles * feat(date-picker): stories added * fix(date-picker): calendar width properly handled * feat(date-picker): styles simplified * chore(date-picker): almost all test passing * fix(date-picker): test and styles * chore(date-picker): calendar popover tests added * fix(date-picker): props to be passed to the date-input * TimeInput Component 🕒 (#2672) * feat(time-input): time input added with some stories, tests and date-picker integration missing * feat(time-input): tests added, date-picker integration added, missing stories added * chore(react): missing packages added * chore(time-input): fix stories names * fix(time-input): time value type * fix: date-picker visibleMonth width does not get widen enough (#2703) * DateRangePicker Component 🗓️ (#2682) * chore(date-range-picker): in progress * chore(date-range-picker): in progress * feat(date-input): components separated into multiple pieces to be able to implement the date range picker * feat(date-range-picker): first version of it working * chore(date-picker): hyphen symbol changed * feat(date-range-picker): stories done * fix(range-calendar): styles * docs: Calendar & RangeCalendar (#2686) * feat(docs): add calendar in routes.json * feat(docs): refresh search-meta.json * feat(docs): add calendar examples * feat(docs): calendar content * feat(deps): add @internationalized/date * refactor(docs): remove div wrapper * feat(docs): add calendar doc * fix(docs): calendar presets * fix(docs): preset styles * chore(docs): remove calendar iframe examples * refactor(docs): discard iframe in calendar doc * fix(docs): incorrect DateValue import * feat(docs): include @internationalized/date in live demo scope * feat(docs): add presets description * chore(docs): update search-meta.json * fix(docs): remove DateValue * feat(docs): include reactAriaI18n in react live demo scope * fix(docs): presets import issue * chore(docs): update search-meta.json * feat(docs): add api reference for nextui provider * fix(calendar): ixExpanded typo * feat(docs): add missing props & event * chore(docs): update search-meta.json * chore(docs): update route keywords * chore(docs): revise value style add defaultFocusedValue * chore(docs): remove padding and revise gap * feat(docs): range calendar * chore(docs): update search-meta.json * feat(docs): add reactAriaHook * fix(docs): incorrect component and add storybook and reactAriaHook * fix(docs): incorrect import path * chore(docs): reorder range calendar position in sidebar * chore(Docs): remove custom styles & implementation * chore(docs): remove last item from accessibility * chore(docs): onValueChange -> onChange * feat(docs): add ts example for range calendar * chore(docs): remove unwanted content in range calendar * feat(docs): add ts examples for calendar * chore(docs): update import path * chore(docs): update import path * chore(docs): styles adjusted, routes updated --------- Co-authored-by: Junior Garcia <[email protected]> * docs: TimeInput (#2698) * feat(docs): add time input to routes.json * feat(deps): add @internationalized/date * feat(docs): add @internationalized/date and @react-aria/i18n to code demo scopes * feat(docs): time input contetnt * chore(docs): revise time input examples * feat(docs): time input content * chore(time-input): update description * feat(docs): add ts examples in time-input * chore(docs): revise TimeValue import --------- Co-authored-by: Junior Garcia <[email protected]> * chore(date-picker): exports updated * docs: DatePicker (#2700) * docs: created the doc for datepicker and its examples * docs: regenerate search-meta.json * fix: reverted the unncessary change to Input component * fix: fixed the component-link for date-picker * fix: fixed the component-link for date-picker * fix: added variants section to the doc * fix: made adjustment to the explanations for the props of DatePicker comp --------- Co-authored-by: Junior Garcia <[email protected]> * doc: DateInput (#2711) * docs: created base examples and the document * chore: created search-meta and follow-up fix for each date-input example cases * fix: fixed some example components styles * fix(docs): updated routes.json * fix(docs): fixed typo in the docs * fix: fixed the component-link for date-input * fix: fixed the component-link for date-input * fix: label-placements example flex style adjustment * fix: added variants section to the doc --------- Co-authored-by: HaRuki Kuriwada <[email protected]> Co-authored-by: Junior Garcia <[email protected]> * refactor(theme): units removed, tailwind-variants upgraded (#2713) * fix(theme): units replaced by spacing * fix(select): positioning the label if a description is used (#2553) Co-authored-by: Poli Sour <[email protected]> * Upgrade to new react aria version (#2561) * chore(root): pkg upgraded * fix: type error * fix: build error * chore: update packages from a~d * chore: update packages from i~r * chore: update packages from s~u * chore: update core, hooks, and utilities packages * feat: add support radio group validationBehavior props * fix: validationBehavior default to native * chore: add validationBehavior props in RadioGroup Stories * fix: handling of errorMessage * chore: add support validationBehavior autocomplete * chore: partial support for validation of select * chore: add support validationBehavior checkbox * chore: change validationBehavior default to native * Merge branch 'v.2.3.0' into feat/upgrade-react-aria * fix: validation logic * fix: add default value for autocomplete * chore: add example using error message function * chore: fixed error displayed in storybook * chore: omit validationBehavior from component props * chore: update docs and storybook on validate * fix: pnpm-lock version --------- Co-authored-by: Junior Garcia <[email protected]> * fix(core): build and date input / time input apis * chore(date-picker): omit validation behavior * chore(docs): add missing props to calendar and range calendar * docs: add nextui-cli page (#2714) * docs: add nextui-cli page * docs: update search meta * docs: typo * docs: typo * docs: typo * feat(docs): cli docs done --------- Co-authored-by: Junior Garcia <[email protected]> * chore(docs): add cli commands to installation docs * fix(checkbox): prettier * fix(docs): incorrect cli api references link * doc: DateRangePicker (#2712) * chore: created base for date-range-picker doc * fix: added follow-up story examples to the doc * fix: fixed bugs happening on the doc * fix: fixed bugs happening on the doc * fix(docs): incorrect file path and revise title * fix: component examples style fixes * fix: component presets typo fix * refactor(core): date range picker docs completed, standaline date picker field fixed --------- Co-authored-by: HaRuki Kuriwada <[email protected]> Co-authored-by: աɨռɢӄաօռɢ <[email protected]> Co-authored-by: Junior Garcia <[email protected]> * fix: only two keyframes currently supported with spring and inertia animations (#2596) * chore(deps): bump framer-motion * feat(changeset): fixed framer motion issue * chore(changeset): revise changeset message * chore(deps): update pnpm-lock.yaml * fix: react hook form issue (#2603) * fix(input): pass domRef?.current?.value to controlled state * fix(input): pass domRef?.current?.value to useTextField instead * fix(checkbox): handle RHF case * fix(checkbox): add missing isSelected case * chore(checkbox): update ref type * chore(deps): add @nextui-org/use-safe-layout-effect * chore(deps): update pnpm-lock.yaml * chore(deps): update pnpm-lock.yaml * fix(select): handle RHF case * chore(deps): add @nextui-org/use-safe-layout-effect to select * fix(autocomplete): handle RHF case * chore(deps): add @nextui-org/use-safe-layout-effect to autocomplete * refactor(components): revise comments * feat(changeset): react-hook-form uncontrolled components * chore(deps): pnpm-lock.yaml * fix(input): domRef.current.value has higher precedence * fix(checkbox): set isChecked based on input ref checked * feat(components): tabs component add tabPosition prop (#2398) * feat(components): tabs component add tabPosition prop * fix: review problem change * test: add tabs position vertical test * docs: update changeset * fix(tabs): optimize return of tabs * fix(tabs): rename orientation to placement * fix(tabs): optimize description * chore(docs): routes * fix: isReadOnly in Autocomplete MDX (#2444) * feat(autocomplete): add isReadOnly example * fix(autocomplete): isReadOnly logic in Autocomplete * feat(root): add changeset - fixed isReadOnly logic in Autocomplete * chore(autocomplete component) isReadOnly property demo isReadOnly property demo in website MDX for autocomplete component. * Update apps/docs/content/docs/components/autocomplete.mdx Co-authored-by: Junior Garcia <[email protected]> --------- Co-authored-by: աɨռɢӄաօռɢ <[email protected]> Co-authored-by: Alpha <[email protected]> Co-authored-by: Junior Garcia <[email protected]> * fix(select): only trigger setSelectedKeys when domRef.current.value is true (#2722) * chore(docs): blog changes (#2724) * chore(docs): blog changes * feat(docs): blog improved * chore(blog): draft param added * chore: version changeset added * feat(blog): v2.3.0 almost done * chore(docs): tailwind colors updated, calendar overflow fixed * chore(blog): add presets demo * fix(calendar): overflow on windows * chore(docs): improve popover placements demo * fix(autocomplete): set shouldUseVirtualFocus to false in getListboxProps (#2731) * chore(blog): add cotributors * chore(blog): draft --------- Co-authored-by: աӄա <[email protected]> Co-authored-by: Shrinidhi Upadhyaya <[email protected]> Co-authored-by: shrinidhi.upadhyaya <[email protected]> Co-authored-by: winches <[email protected]> Co-authored-by: HaRuki <[email protected]> Co-authored-by: HaRuki Kuriwada <[email protected]> Co-authored-by: Poli Sour <[email protected]> Co-authored-by: Poli Sour <[email protected]> Co-authored-by: Ryo Matsukawa <[email protected]> Co-authored-by: winches <[email protected]> Co-authored-by: Alpha Xek <[email protected]> Co-authored-by: Alpha <[email protected]>
build & tests issues will be handled in PR #2561📝 Description
Framer Motion previously introduced a bug in v11 and NextUI was stuck using v10. Framer motion team fixed that and released 13 hours ago. This PR is to bump to frame motion version to include that fix.
⛳️ Current behavior (updates)
With
[email protected]
pr-2596-issue-demo.webm
🚀 New behavior
pr2596-demo.webm
💣 Is this a breaking change (Yes/No):
No
📝 Additional Information
Summary by CodeRabbit
Summary by CodeRabbit
framer-motion
package across various components and utilities to version11.0.22
for enhanced performance and consistency.[email protected]
and[email protected]
across the board.