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

feat(types,clerk-js): Introduce user hasVerifiedEmailAddress & hasVerifiedPhoneNumber attributes #300

Merged
merged 1 commit into from
Jul 1, 2022

Conversation

chanioxaris
Copy link
Member

Type of change

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

Packages affected

  • @clerk/clerk-js
  • @clerk/clerk-react
  • @clerk/nextjs
  • @clerk/remix
  • @clerk/types
  • @clerk/clerk-expo
  • @clerk/backend-core
  • @clerk/clerk-sdk-node
  • @clerk/edge
  • build/tooling/chore

Description

  • npm test runs as expected.
  • npm run build runs as expected.

Introduce 2 new attributes on the User resource

  • hasVerifiedEmailAddress: denote if the user has at least one verified email address
  • hasVerifiedPhoneNumber: denote if the user has at least one verified phone number

…ifiedPhoneNumber attributes

Introduce 2 new attributes on the User resource, hasVerifiedEmailAddress & hasVerifiedPhoneNumber. Those denote if the user has at least one verified email address & phone number respectively
Copy link
Contributor

@igneel64 igneel64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 🍰

@chanioxaris chanioxaris merged commit fb0c00d into main Jul 1, 2022
@chanioxaris chanioxaris deleted the user-attribute-verified-email-phone branch July 1, 2022 08:36
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants