From aec38ab43b5068261c676f97cd4c3f70b54c2a5a Mon Sep 17 00:00:00 2001 From: Hui Zhao Date: Mon, 14 Apr 2025 14:03:28 -0700 Subject: [PATCH] fix: incorrect arrow function expression --- .../auth/auth-migration-guide/index.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/pages/gen1/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx b/src/pages/gen1/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx index 34cb11654fa..b5e99877913 100644 --- a/src/pages/gen1/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx +++ b/src/pages/gen1/[platform]/build-a-backend/auth/auth-migration-guide/index.mdx @@ -301,7 +301,7 @@ Also notice that `userConfirmed` is no longer returned, and instead we return `n const handleConfirmSignUp = async ({ username, confirmationCode - }) { + }) => { await Auth.confirmSignUp(username, confirmationCode); } @@ -455,7 +455,7 @@ In v6, `confirmSignUp` now takes named parameters instead of positional paramete const handleConfirmSignUp = async ({ username, confirmationCode - }) { + }) => { const { isSignUpComplete, userId, @@ -475,7 +475,7 @@ In v6, `confirmSignUp` now takes named parameters instead of positional paramete const handleConfirmSignUp = async ({ username, confirmationCode - }) { + }) => { await Auth.confirmSignUp( username, confirmationCode @@ -498,7 +498,7 @@ In v6, `confirmSignUp` now takes named parameters instead of positional paramete const handleConfirmSignUp = async ({ username, confirmationCode - }) { + }) => { const { isSignUpComplete, userId, @@ -522,7 +522,7 @@ In v6, `confirmSignUp` now takes named parameters instead of positional paramete const handleConfirmSignUp = async ({ username, confirmationCode - }) { + }) => { await Auth.confirmSignUp( username, confirmationCode,