Skip to content

chore: Rely on API-based errors for en-US messaging #5809

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

Merged
merged 4 commits into from
May 5, 2025

Conversation

tmilewski
Copy link
Member

Description

Simply put, this is meant to rely on the API for en-US-based error messaging.

FIXES ECO-632

Checklist

  • pnpm test runs as expected.
  • pnpm 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:

@tmilewski tmilewski self-assigned this May 2, 2025
Copy link

changeset-bot bot commented May 2, 2025

🦋 Changeset detected

Latest commit: a764aaa

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

This PR includes changesets to release 4 packages
Name Type
@clerk/localizations Minor
@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

Copy link

vercel bot commented May 2, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 5, 2025 1:54pm

@tmilewski tmilewski force-pushed the tm/eco-632-set-initial-en-us-error-msgs-undefined branch from 9274935 to 5ec2015 Compare May 5, 2025 13:26
@tmilewski tmilewski merged commit b9d90da into main May 5, 2025
31 of 32 checks passed
@tmilewski tmilewski deleted the tm/eco-632-set-initial-en-us-error-msgs-undefined branch May 5, 2025 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants