From 32fd3d46824dab2d40b3c515f6d456725e1d2e30 Mon Sep 17 00:00:00 2001 From: Rene Brandel <4989523+renebrandel@users.noreply.github.com> Date: Tue, 23 Jan 2024 19:37:09 -0500 Subject: [PATCH] Clarified "Legacy" designation in Auth.signUp/Auth.signIn (#6746) --- .../build-a-backend/auth/auth-migration-guide/index.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx b/src/pages/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx index 055a7d9212c..b900b2669f2 100644 --- a/src/pages/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx +++ b/src/pages/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx @@ -325,6 +325,8 @@ Also notice that `userConfirmed` is no longer returned, and instead we return `n ### Legacy +In the past, we've supported the ability to pass in `username`, `password`, `email`, `phone_number` as positional parameters instead of as named input parameters for `Auth.signUp` for backwards compatibility with older versions of Amplify JavaScript. The following guide shows you how to migrate from that legacy call pattern for `Auth.signUp`: + ```js @@ -947,6 +949,8 @@ Also notice that `challengeName` and `challengeParam` (returned in v5 as additio ### Legacy +In the past, we've supported the ability to pass in `username`, `password` as positional parameters instead of as named input parameters for `Auth.signIn` for backwards compatibility with older versions of Amplify JavaScript. The following guide shows you how to migrate from that legacy call pattern for `Auth.signIn`: + ```js