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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@aws-amplify/[email protected]
Major Changes
#745
3ead9c629
Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & VueThe
Authenticator
has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.See: RFC: Authenticator@next
Goals
Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.
Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.
Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.
Interoperable – Work with password managers, autofill, existing styles, & other common features.
Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.
Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.
Learn more by visiting the Authenticator Documentation.
Minor Changes
#626
f84e9949b
Thanks @ericclemmons! - ## Zero ConfigurationAs of
@aws-amplify/[email protected]
,aws-exports.js
includes your backend configuration for the Authenticator to automatically inferloginMechanisms
andsocialProviders
.Before (React)
After (React)
Sign in with Apple
The Authenticator supports
apple
as one of manysocialProviders
. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/#610
1fc955c4e
Thanks @wlee221! - Addsign-up-form-field
slot and component#627
bd3e09a09
Thanks @wlee221! - This implementsAuthenticatorService
that can be used internally and externally to access common Authenticator context and helpers.Usage:
app.component.ts
app.component.html
#628
ef1e0f000
Thanks @wlee221! - Add and expose amplify-checkbox#628
ef1e0f000
Thanks @wlee221! - Addservices
prop and custom-sign-up example. See documentation for usage notes.Patch Changes
#695
d5009572c
Thanks @ericclemmons! - ## Header & Footer SlotsUpdated dependencies [
bba3242af
,f84e9949b
,e76c5ac17
,81169c66e
,3cc1c15d7
,2b2ae8469
,b46597cef
,edea9ffaa
,bd3e09a09
,70552a4cc
,beb9b49b5
,5257a3109
,3ead9c629
]:@aws-amplify/[email protected]
Major Changes
#747
81169c66e
Thanks @wlee221! - New primitive components and theming APIAmplify UI is building primitive components like badges, cards, alerts, etc. These primitive components will first be available on React with the goal of adding support for more frameworks in the future. We hope these primitives will empower developers to build applications faster. We plan on building out more connected components like the Authenticator and we need primitive components like buttons and inputs to be shared across them. Exposing these primitive components allows developers to create and theme applications end-to-end using the same components everywhere.
See: RFC: Amplify UI Primitive Components
Goals
Flexible – Primitives can be integrated into as many applications as possible.
Customizable – Primitives can be composed and styled using a theme, CSS, a CSS-in-JS framework, or un-styled.
Accessible – Primitives follow WCAG and WAI-ARIA guidelines to make building accessible applications easy.
Basic
Implementation
#745
3ead9c629
Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & VueThe
Authenticator
has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.See: RFC: Authenticator@next
Goals
Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.
Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.
Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.
Interoperable – Work with password managers, autofill, existing styles, & other common features.
Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.
Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.
Learn more by visiting the Authenticator Documentation.
Minor Changes
#626
f84e9949b
Thanks @ericclemmons! - ## Zero ConfigurationAs of
@aws-amplify/[email protected]
,aws-exports.js
includes your backend configuration for the Authenticator to automatically inferloginMechanisms
andsocialProviders
.Before (React)
After (React)
Sign in with Apple
The Authenticator supports
apple
as one of manysocialProviders
. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/#650
e76c5ac17
Thanks @ericclemmons! - ##signUpAttributes
The Sign Up form will include most of https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-attributes.html by default with zero-config.
Any verification mechanisms (e.g.
email
,phone_number
) will always be required.#698
5482edcbb
Thanks @reesscot! - Add forwardRef support to Button & View#716
e155ef0be
Thanks @reesscot! - Remove AmplifyProvider custom components feature#717
edea9ffaa
Thanks @dbanksdesign! - Adding card variations#653
70552a4cc
Thanks @reesscot! - Icon size now matches parent font-size. Allows customers to more easily use icons alongsize Headings, Buttons, etc.Example:
#582
3143deff1
Thanks @ericclemmons! - AmplifyProvider accepts a partial list of primitives ascomponents
:Patch Changes
#737
8f0301f0b
Thanks @reesscot! - ForwardRef support - CountryCode, SelectField, and SliderField#552
bba3242af
Thanks @ericclemmons! -@aws-amplify/ui-react
supports validation & re-use & customization ofAuthenticator.SignUp.FormFields
viacomponents
&services
:#617
77fa42da5
Thanks @hvergara! - Fix primitives catalog generator#720
84a86b4ef
Thanks @reesscot! - ForwardRef support - Flex and Grid#761
a82e422f3
Thanks @reesscot! - ForwardRef support for TextField#709
3cc1c15d7
Thanks @dbanksdesign! - Building icons from Figma source now.#618
943d4b661
Thanks @hvergara! - Make style prop types more flexible#636
5e31719f1
Thanks @hvergara! - useStorageURL React hook#725
8f4d8129c
Thanks @reesscot! - ForwardRef support - misc view-based primitives#601
f6d144dc3
Thanks @hvergara! - Add useAuth React hook#731
c5ae2f44a
Thanks @reesscot! - ForwardRef support - textarea, checkbox, radio#568
36d256b02
Thanks @slaymance! - Adds React Table primitive#727
2b2ae8469
Thanks @dbanksdesign! - * Divider component has more theming options for the border style, color, and width.#721
e90085e1d
Thanks @reesscot! - Forward ref inputs#695
d5009572c
Thanks @ericclemmons! - ## Header & Footer Slots#719
df2bcb749
Thanks @reesscot! - ForwardRef support - base primitives#612
beb9b49b5
Thanks @reesscot! - Menu primitiveNew primitive which enables customers to create aaccessible, interactive menu for selecting actions within an application.
Dropdown menu is collision-aware and will automatically change location based on available space.
#638
d71e65609
Thanks @ericclemmons! - Fix getOverrideProps to return all, not just 2#634
5257a3109
Thanks @dbanksdesign! - Adding support for token style props in React components and movingcreateTheme
inside the AmplifyProvider so users don't have to call it directly in React.Then using theme tokens in a style prop:
The ui-react package is now exporting the
Theme
type to make it easier to define a theme object outside of thecreateTheme
method.#748
ca04c8dbc
Thanks @reesscot! - Remove internal fieldgroup exportUpdated dependencies [
bba3242af
,f84e9949b
,e76c5ac17
,81169c66e
,3cc1c15d7
,2b2ae8469
,b46597cef
,edea9ffaa
,bd3e09a09
,70552a4cc
,beb9b49b5
,5257a3109
,3ead9c629
]:@aws-amplify/[email protected]
Major Changes
#747
81169c66e
Thanks @wlee221! - New primitive components and theming APIAmplify UI is building primitive components like badges, cards, alerts, etc. These primitive components will first be available on React with the goal of adding support for more frameworks in the future. We hope these primitives will empower developers to build applications faster. We plan on building out more connected components like the Authenticator and we need primitive components like buttons and inputs to be shared across them. Exposing these primitive components allows developers to create and theme applications end-to-end using the same components everywhere.
See: RFC: Amplify UI Primitive Components
Goals
Flexible – Primitives can be integrated into as many applications as possible.
Customizable – Primitives can be composed and styled using a theme, CSS, a CSS-in-JS framework, or un-styled.
Accessible – Primitives follow WCAG and WAI-ARIA guidelines to make building accessible applications easy.
Basic
Implementation
#745
3ead9c629
Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & VueThe
Authenticator
has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.See: RFC: Authenticator@next
Goals
Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.
Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.
Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.
Interoperable – Work with password managers, autofill, existing styles, & other common features.
Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.
Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.
Learn more by visiting the Authenticator Documentation.
Minor Changes
#626
f84e9949b
Thanks @ericclemmons! - ## Zero ConfigurationAs of
@aws-amplify/[email protected]
,aws-exports.js
includes your backend configuration for the Authenticator to automatically inferloginMechanisms
andsocialProviders
.Before (React)
After (React)
Sign in with Apple
The Authenticator supports
apple
as one of manysocialProviders
. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/#650
e76c5ac17
Thanks @ericclemmons! - ##signUpAttributes
The Sign Up form will include most of https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-attributes.html by default with zero-config.
Any verification mechanisms (e.g.
email
,phone_number
) will always be required.#717
edea9ffaa
Thanks @dbanksdesign! - Adding card variations#627
bd3e09a09
Thanks @wlee221! - This implementsAuthenticatorService
that can be used internally and externally to access common Authenticator context and helpers.Usage:
app.component.ts
app.component.html
#653
70552a4cc
Thanks @reesscot! - Icon size now matches parent font-size. Allows customers to more easily use icons alongsize Headings, Buttons, etc.Example:
Patch Changes
#552
bba3242af
Thanks @ericclemmons! -@aws-amplify/ui-react
supports validation & re-use & customization ofAuthenticator.SignUp.FormFields
viacomponents
&services
:#709
3cc1c15d7
Thanks @dbanksdesign! - Building icons from Figma source now.#727
2b2ae8469
Thanks @dbanksdesign! - * Divider component has more theming options for the border style, color, and width.#615
b46597cef
Thanks @reesscot! - Applybox-sizing: border-box
styling to all Amplify theme children#612
beb9b49b5
Thanks @reesscot! - Menu primitiveNew primitive which enables customers to create aaccessible, interactive menu for selecting actions within an application.
Dropdown menu is collision-aware and will automatically change location based on available space.
#634
5257a3109
Thanks @dbanksdesign! - Adding support for token style props in React components and movingcreateTheme
inside the AmplifyProvider so users don't have to call it directly in React.Then using theme tokens in a style prop:
The ui-react package is now exporting the
Theme
type to make it easier to define a theme object outside of thecreateTheme
method.@aws-amplify/[email protected]
Major Changes
#745
3ead9c629
Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & VueThe
Authenticator
has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.See: RFC: Authenticator@next
Goals
Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.
Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.
Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.
Interoperable – Work with password managers, autofill, existing styles, & other common features.
Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.
Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.
Learn more by visiting the Authenticator Documentation.
Minor Changes
#626
f84e9949b
Thanks @ericclemmons! - ## Zero ConfigurationAs of
@aws-amplify/[email protected]
,aws-exports.js
includes your backend configuration for the Authenticator to automatically inferloginMechanisms
andsocialProviders
.Before (React)
After (React)
Sign in with Apple
The Authenticator supports
apple
as one of manysocialProviders
. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/#627
bd3e09a09
Thanks @wlee221! - This implementsAuthenticatorService
that can be used internally and externally to access common Authenticator context and helpers.Usage:
app.component.ts
app.component.html
Patch Changes
#695
d5009572c
Thanks @ericclemmons! - ## Header & Footer SlotsUpdated dependencies [
bba3242af
,f84e9949b
,e76c5ac17
,81169c66e
,3cc1c15d7
,2b2ae8469
,b46597cef
,edea9ffaa
,bd3e09a09
,70552a4cc
,beb9b49b5
,5257a3109
,3ead9c629
]: