nhost

Patch Changes

• @nhost/[email protected]

Patch Changes

• @nhost/[email protected]

Patch Changes

• @nhost/[email protected]
• @nhost/[email protected]

Patch Changes

• 65a3061: correct cookie storage type

Patch Changes

• 58fa2a2: Improve loading status
  The loading status indicates the authentication is not yet known to the client when it starts. Once the client is ready, the authentication status is either signed in, or signed out.
  When the user was trying to authenticate, the loading status was set to true until the result of the authentication was known.
  The client now only return loading: true on startup, and in no other cases.
• 58fa2a2: Look for a valid refresh token both the URL and local storage
  When auto-signin was activated, the client was not taking into account the refresh token in the URL if a token was already stored locally.
  The user was then not able to authenticate from a link when the refresh token stored locally was invalid or expired.
  When auto-signin is activated, the client now checks and tries tokens from both the URL and the local storage, starting with the URL.

Patch Changes

• Updated dependencies [58fa2a2]
• Updated dependencies [58fa2a2]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• 58fa2a2: Improve loading status
  The loading status indicates the authentication is not yet known to the client when it starts. Once the client is ready, the authentication status is either signed in, or signed out.
  When the user was trying to authenticate, the loading status was set to true until the result of the authentication was known.
  The client now only return loading: true on startup, and in no other cases.
• 58fa2a2: Look for a valid refresh token both the URL and local storage
  When auto-signin was activated, the client was not taking into account the refresh token in the URL if a token was already stored locally.
  The user was then not able to authenticate from a link when the refresh token stored locally was invalid or expired.
  When auto-signin is activated, the client now checks and tries tokens from both the URL and the local storage, starting with the URL.
• Updated dependencies [58fa2a2]
• Updated dependencies [58fa2a2]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• 58fa2a2: Improve loading status
  The loading status indicates the authentication is not yet known to the client when it starts. Once the client is ready, the authentication status is either signed in, or signed out.
  When the user was trying to authenticate, the loading status was set to true until the result of the authentication was known.
  The client now only return loading: true on startup, and in no other cases.
• 58fa2a2: Look for a valid refresh token both the URL and local storage
  When auto-signin was activated, the client was not taking into account the refresh token in the URL if a token was already stored locally.
  The user was then not able to authenticate from a link when the refresh token stored locally was invalid or expired.
  When auto-signin is activated, the client now checks and tries tokens from both the URL and the local storage, starting with the URL.
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [58fa2a2]
• Updated dependencies [58fa2a2]
  • @nhost/[email protected]

Patch Changes

• Updated dependencies [58fa2a2]
• Updated dependencies [58fa2a2]
  • @nhost/[email protected]

Patch Changes

• 58fa2a2: Improve loading status
  The loading status indicates the authentication is not yet known to the client when it starts. Once the client is ready, the authentication status is either signed in, or signed out.
  When the user was trying to authenticate, the loading status was set to true until the result of the authentication was known.
  The client now only return loading: true on startup, and in no other cases.
• 58fa2a2: Look for a valid refresh token both the URL and local storage
  When auto-signin was activated, the client was not taking into account the refresh token in the URL if a token was already stored locally.
  The user was then not able to authenticate from a link when the refresh token stored locally was invalid or expired.
  When auto-signin is activated, the client now checks and tries tokens from both the URL and the local storage, starting with the URL.
• Updated dependencies [58fa2a2]
• Updated dependencies [58fa2a2]
  • @nhost/[email protected]

Minor Changes

• 42edb74: Adapt to React 18

Patch Changes

• b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter
• b56162a: Introduce 'custom' client storage type
• b56162a: Introduce a new 'cookie' client storage type
• 54e1873: Fix: add authentication headers to GraphQL operations when authenticated
• Updated dependencies [54e1873]
  • @nhost/[email protected]
  • @nhost/[email protected]

Patch Changes

• b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter
• 185f39e: Don't take previous errors into account when using SMS and deanonymisation
  When using the SMS and anonymous signing methods of the Nhost client, the action failed with the client's previous error.
• Updated dependencies [b56162a]
  • @nhost/[email protected]

Minor Changes

• 42edb74: Adapt to React 18

Patch Changes

• b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter

• 1fb51a7: Rename user data hooks to make them all start with userUser...
  The hooks that help to access user data were not consistently named.
  The following hooks have been therefore renamed:

  • useAvatarUrl -> useUserAvatarUrl
  • useDefaultRole -> useUserDefaultRole
  • useDisplayName -> useUserDisplayName
  • useEmail -> useUserEmail
  • useIsAnonymous -> useUserIsAnonymous

  Their former names are still available for backwards compatibility, but are flagged as deprecated.

• 54e1873: Fix: add authentication headers to GraphQL operations when authenticated

• Updated dependencies [185f39e]

  • @nhost/[email protected]

Minor Changes

• 42edb74: Adapt to React 18
• 42edb74: Bump to Apollo client 3.6.2

Patch Changes

• 54e1873: Fix: add authentication headers to GraphQL operations when authenticated
• Updated dependencies [42edb74]
  • @nhost/[email protected]
  • @nhost/[email protected]

Minor Changes

• 42edb74: Bump to Apollo client 3.6.2

Patch Changes

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

Minor Changes

• b56162a: Introduce 'custom' client storage type
• b56162a: Introduce a new 'cookie' client storage type

Patch Changes

• b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter

Patch Changes

• b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter
• 185f39e: Don't take previous errors into account when using SMS and deanonymisation
  When using the SMS and anonymous signing methods of the Nhost client, the action failed with the client's previous error.
• Updated dependencies [185f39e]
  • @nhost/[email protected]

Patch Changes

• @nhost/[email protected]
• @nhost/[email protected]

Patch Changes

• Updated dependencies [7b23d33]
  • @nhost/[email protected]