nhost

Minor Changes

• 6f0a3005: sendMfaOtp now returns a promise
  When using useSignInEmailPassword, the sendMfaOtp was void. It now returns a promise that resolves when the server returned the result of the OTP code submission, and returns isSuccess, isError, and error.

Patch Changes

• 756d9960: correct useResetPassword inline example
• Updated dependencies [6f0a3005]
• Updated dependencies [6f0a3005]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• 6f0a3005: Complete sign-in when email+password MFA is activated
  It was not possible to complete authentication with nhost.auth.signIn in sending the TOTP code when email+password MFA was activated.
  An user that activated MFA can now sign in with the two following steps:

  await nhost.auth.signIn({ email: '[email protected]', password: 'not-my-birthday' })
  // Get the one-time password with an OTP application e.g. Google Authenticator
  await nhost.auth.signIn({ otp: '123456' })
  

Patch Changes

• Updated dependencies [6f0a3005]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [6f0a3005]
• Updated dependencies [6f0a3005]
  • @nhost/[email protected]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [6f0a3005]
• Updated dependencies [6f0a3005]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• 6f0a3005: Complete sign-in when email+password MFA is activated
  It was not possible to complete authentication with nhost.auth.signIn in sending the TOTP code when email+password MFA was activated.
  An user that activated MFA can now sign in with the two following steps:

  await nhost.auth.signIn({ email: '[email protected]', password: 'not-my-birthday' })
  // Get the one-time password with an OTP application e.g. Google Authenticator
  await nhost.auth.signIn({ otp: '123456' })
  

Patch Changes

• Updated dependencies [6f0a3005]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [6f0a3005]
  • @nhost/[email protected]

Patch Changes

• 6f45856c: Correct use of ref values in action options
  The nestedUnref helper was not correctly un-refing nested values. For instance, the values the properties of the following metadata were still refs:

  const { signUpEmailPassword } = useSignUpEmailPassword()
  const firstName = ref('John')
  const lastName = ref('Doe')
  signUpEmailPassword((email: '[email protected]'), (password: 'not-1234'), {
    metadata: { firstName, lastName }
  })
  

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]

Minor Changes

• c1613394: Deanonymisation
  Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize.
  Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• c1613394: Deanonymisation
  Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize.
  Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]

Minor Changes

• c1613394: Extend deanonymisation options
  The Nhost Auth client method auth.deanonymize was only accepting allowedRoles and defaultRole as additional parameters. It is not possible to pass on an options parameter with the usual registration options such as redirectTo, locale, metadata, and displayName.
  The auth.deanonymize parameters are now strongly typed.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]

Minor Changes

• c1613394: Deanonymisation
  Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize.
  Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• c1613394: Deanonymisation
  Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize.
  Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [c1613394]
• Updated dependencies [c1613394]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• c1613394: Deanonymisation
  Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize.
  Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

• Updated dependencies [c1613394]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [8b2d1b00]
  • @nhost/[email protected]

Patch Changes

• 8b2d1b00: Add headers to the websocket connection when creating the Apollo client

Patch Changes

• Updated dependencies [08a37aae]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [08a37aae]
  • @nhost/[email protected]
  • @nhost/[email protected]