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(ui): Render phone number error message #3744

Conversation

alexcarpenter
Copy link
Member

Description

Add error message rendering to <PhoneNumberField />

Screenshot 2024-07-17 at 10 14 14 AM

https://linear.app/clerk/issue/SDKI-118/signin-start-phone-field-error-not-displaying-when-an-account-isnt

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:

Copy link

changeset-bot bot commented Jul 17, 2024

🦋 Changeset detected

Latest commit: 066274b

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

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@alexcarpenter alexcarpenter requested a review from tmilewski July 17, 2024 14:17
@alexcarpenter alexcarpenter enabled auto-merge (squash) July 17, 2024 14:36
@alexcarpenter alexcarpenter merged commit bfdd9c1 into main Jul 17, 2024
16 checks passed
@alexcarpenter alexcarpenter deleted the alexcarpenter/sdki-118-signin-start-phone-field-error-not-displaying-when-an branch July 17, 2024 14:43
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.

2 participants