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: Normalise phoneNumber received in the input before processing #881

Conversation

anku255
Copy link
Contributor

@anku255 anku255 commented Nov 16, 2023

Summary of change

This pull request introduces phone number normalisation to all API endpoints that accept phone numbers as user input. The implementation includes the addition of a normaliseIfPhoneNumber function in the Utils class, which is now utilized across all relevant APIs.

Related issues

#880

Test Plan

I've added test cases to ensure the proper normalization of phone numbers by the normaliseIfPhoneNumber utility function. Additionally, I've added corresponding test cases in all modified APIs to validate this behavior.

Documentation changes

(If relevant, please create a PR in our docs repo, or create a checklist here
highlighting the necessary changes)

Checklist for important updates

  • Changelog has been updated
    • If there are any db schema changes, mention those changes clearly
  • coreDriverInterfaceSupported.json file has been updated (if needed)
  • pluginInterfaceSupported.json file has been updated (if needed)
  • Changes to the version if needed
    • In build.gradle
  • If added a new paid feature, edit the getPaidFeatureStats function in FeatureFlag.java file
  • Had installed and ran the pre-commit hook
  • If there are new dependencies that have been added in build.gradle, please make sure to add them
    in implementationDependencies.json.
  • Update function getValidFields in io/supertokens/config/CoreConfig.java if new aliases were added for any core config (similar to the access_token_signing_key_update_interval config alias).
  • Issue this PR against the latest non released version branch.
    • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the
      latest branch (git branch --all) whose X.Y is greater than the latest released tag.
    • If no such branch exists, then create one from the latest released branch.
  • If added a foreign key constraint on app_id_to_user_id table, make sure to delete from this table when deleting the user as well if deleteUserIdMappingToo is false.

@anku255 anku255 changed the title Normalise phoneNumber received in the input before processing feat: Normalise phoneNumber received in the input before processing Nov 16, 2023
@anku255 anku255 force-pushed the feat/phone-number-normalisation-api-changes branch from e1c7463 to 6b2657c Compare November 16, 2023 11:24
@anku255 anku255 force-pushed the feat/phone-number-normalisation-base branch from 15cb479 to b0fa0dd Compare November 16, 2023 11:24
@rishabhpoddar rishabhpoddar merged commit f93d7e2 into feat/phone-number-normalisation-base Nov 16, 2023
2 of 3 checks passed
@rishabhpoddar rishabhpoddar deleted the feat/phone-number-normalisation-api-changes branch November 16, 2023 16:28
rishabhpoddar pushed a commit that referenced this pull request Nov 20, 2023
… Migration script (#885)

* feat: Normalise phoneNumber received in the input before processing (#881)

* feat: normalise phoneNumber received in the input before processing

* feat: PR changes

* feat: PR changes

* feat: Improve test for invalid phone number inputs (#884)

* feat: Add migration script for phone number normalisation (#882)

* feat: Add migration script for phone number normalisation

* feat: PR changes

* feat: PR changes

* feat: PR changes

* feat: PR changes

* feat: PR changes

* feat: PR changes
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