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

fix(clerk-js): Handle gracefully yet unknown to our components Web3 providers #4263

Conversation

chanioxaris
Copy link
Member

Description

If FAPI returns a Web3 provider that is not yet known to our types and components, then we fail to render them. We fix that by filtering them out, as we do for OAuth

Before

Screenshot 2024-10-01 at 9 58 43 AM

After

Screenshot 2024-10-01 at 9 59 09 AM

Checklist

  • npm test runs as expected.
  • npm run build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

…roviders

If FAPI returns a Web3 provider that is not yet known to our types and components,
then we fail to render them. We fix that by filtering them out, as we do for OAuth
Copy link

changeset-bot bot commented Oct 1, 2024

🦋 Changeset detected

Latest commit: 7739840

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@clerk/clerk-js Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@chanioxaris chanioxaris merged commit 8568534 into main Oct 1, 2024
21 checks passed
@chanioxaris chanioxaris deleted the haris/user-794-gracefully-handle-unknown-web3-provider-for-clerkjs-v4 branch October 1, 2024 07:31
chanioxaris added a commit that referenced this pull request Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants