Clarified "Legacy" designation in Auth.signUp/Auth.signIn (#6746)

aws-amplify · Jan 24, 2024 · 32fd3d4 · 32fd3d4
1 parent d9bf316
commit 32fd3d4
Showing 1 changed file with 4 additions and 0 deletions.
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
@@ -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`:
+
 <BlockSwitcher>
   <Block name="V6">
     ```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`:
+
 <BlockSwitcher>
   <Block name="V6">
     ```js