Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RELEASE] Update package versions #67

Merged
merged 1 commit into from
Sep 26, 2024
Merged

[RELEASE] Update package versions #67

merged 1 commit into from
Sep 26, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 26, 2024

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.

    <ForceAuth errorFallback={ErrorFallback}>
       App Content
     </ForceAuth>
    
     function ErrorFallback(props: ErrorFallbackProps) {
       return (
         <>
           <Box margin={2} color={"red"}>{props.error.message}</Box>
        </>
       );
     }

    If additional inputs or state must be accessed from within the error fallback component the renderErrorFallback option should be used.

    const userName = "user1";
    <ForceAuth  renderErrorFallback={(e: Error) => (
          <>
              <Box>Could not login {userName}</Box>
              <Box color={"red"}>{e.message}</Box>
           </>
      )}>
      App Content
    </ForceAuth>

    The renderErrorFallback property takes precedence over the errorFallback property.

Patch Changes

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.
  • Updated dependencies [39dad46]

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.
  • Updated dependencies [39dad46]

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.

@open-pioneer/[email protected]

Patch Changes

@open-pioneer/[email protected]

Patch Changes

  • 39dad46: Switch to a new versioning strategy.
    From now on, packages released by this repository share a common version number.

@open-pioneer/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 2 times, most recently from fe7703c to 4a65a23 Compare September 26, 2024 09:52
@mbeckem mbeckem merged commit 5db1a49 into main Sep 26, 2024
@mbeckem mbeckem deleted the changeset-release/main branch September 26, 2024 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant