Skip to content

Releases: aws-amplify/amplify-ui

@aws-amplify/[email protected]

30 Mar 00:19
dcea62f
Compare
Choose a tag to compare

Patch Changes

@aws-amplify/[email protected]

24 Mar 22:12
8278c72
Compare
Choose a tag to compare

Minor Changes

  • #1538 eedae2362 Thanks @joebuono! - Adds the optional hasMorePages prop to the Pagination component

    The reason this is necessary is because sometimes the totalPages count is unknown when pagination occurs at the API level.

    Resulting conditions:

    • Current behavior of totalPages prop stays the same, which determines the page numbers to show
    • A new hasMorePages prop is added to Pagination component
    • When hasMorePages is true, and the customer is at the end of the pages (e.g. 10 of 10), then the next button will NOT be disabled
    • When hasMorePages is false, and the customer is at the end of the pages (e.g. 10 of 10), then the next button WILL be disabled

@aws-amplify/[email protected]

22 Mar 22:15
c070cc8
Compare
Choose a tag to compare

Patch Changes

@aws-amplify/[email protected]

22 Mar 22:15
c070cc8
Compare
Choose a tag to compare

Patch Changes

@aws-amplify/[email protected]

22 Mar 22:15
c070cc8
Compare
Choose a tag to compare

Patch Changes

  • #1548 0e61396c8 Thanks @calebpollman! - chore(react-authenticator): consolidate Authenticator form event handlers in useFormHandlers hook

  • #1343 4896136e9 Thanks @dbanksdesign! - Adding deprecation warnings to icons

  • #1537 c1eed8265 Thanks @reesscot! - fix: suppress erroneous isMultiline deprecation warnings on TextField component

    Deprecation warning messages are showing for users of TextField for the isMultiline prop even though
    they are not using the prop. This issue is fixed by making the shouldWarn prop required on the internal
    useDeprecationWarning hook.

  • Updated dependencies [7910c04b5, 30e3155ac]:

@aws-amplify/[email protected]

22 Mar 22:15
c070cc8
Compare
Choose a tag to compare

Patch Changes

@aws-amplify/[email protected]

17 Mar 17:59
b17828b
Compare
Choose a tag to compare

Patch Changes

  • #1535 f1d4020be Thanks @reesscot! - fix: typo in mapping of TextField left style prop (left was mapped to right, when should be mapped to left)

@aws-amplify/[email protected]

17 Mar 02:51
9ec3f55
Compare
Choose a tag to compare

Patch Changes

  • #1530 3a8925b76 Thanks @reesscot! - fix: update complex field components (TextField, TextAreaField, etc) to apply absolute positioning from Figma

    Figma to Studio integration will absolutely position components when autolayout is not enabled in Figma. This causes an issue for field components that were passing position, top, and left, and padding down to the input element, causing the layout not to match Figma. This is fixed by moving the absolute position props and padding up to the container Flex element.

@aws-amplify/[email protected]

15 Mar 21:45
16f7ced
Compare
Choose a tag to compare

Patch Changes

@aws-amplify/[email protected]

15 Mar 21:45
16f7ced
Compare
Choose a tag to compare

Patch Changes