Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@open-pioneer/[email protected]
Minor Changes
41f0c6f: Introduce new authentication state
AuthStateAuthenticationError
Error state is supposed to be used for errors that occur during the authentication process (e.g. lost connection to authentication backend) rather than for failed login attempts (e.g. invalid credentials)
ForceAuth
component provides two mechanisms to render a fallback component if an authentication error occurs.errorFallback
option takes an abitrary react component that is rendered in case of an error. The error object can be accessed via the ErrorFallbackPros.If additional inputs or state must be accessed from within the error fallback component the
renderErrorFallback
option should be used.The
renderErrorFallback
property takes precedence over theerrorFallback
property.Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.
@open-pioneer/[email protected]
Patch Changes
From now on, packages released by this repository share a common version number.