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

Make OTP template more contextual #7434

Merged
merged 9 commits into from
Jan 12, 2024
Merged

Make OTP template more contextual #7434

merged 9 commits into from
Jan 12, 2024

Conversation

vermakhushboo
Copy link
Member

@vermakhushboo vermakhushboo commented Jan 11, 2024

What does this PR do?

Add more details to the OTP message and generate translations for all languages

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Screenshots may also be helpful.)

Related PRs and Issues

Checklist

  • Have you read the Contributing Guidelines on issues?
  • If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?

@christyjacob4
Copy link
Member

@vermakhushboo the PR looks good at first glance. But I dont think it addresses the issues mentioned. The issues mentioned talk about being able to customise the sms message which we plan to do in a separate feature.

@vermakhushboo
Copy link
Member Author

vermakhushboo commented Jan 11, 2024

@vermakhushboo the PR looks good at first glance. But I dont think it addresses the issues mentioned. The issues mentioned talk about being able to customise the sms message which we plan to do in a separate feature.

@christyjacob4 I agree, but the PR I have created is for the task that was assigned to me.

I think @stnguyen90 added related issues to it. Steven, can we create new tasks for those and assign separately?

@@ -36,6 +36,7 @@
"emails.certificate.footer": "Your previous certificate will be valid for 30 days since the first failure. We highly recommend investigating this case, otherwise your domain will end up without a valid SSL communication.",
"emails.certificate.thanks": "Thanks",
"emails.certificate.signature": "{{project}} team",
"sms.verification.body": "{{secret}} is your {{project}} verification code.",
Copy link
Member

Choose a reason for hiding this comment

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

Actually I think its important for the message to be structured as Your [PROJECT_NAME] verification code is: [CODE]
This will allow the phone operating systems to detect and suggest codes in apps

Copy link
Member Author

Choose a reason for hiding this comment

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

@christyjacob4, @Meldiron and I researched a bit into how other companies do it and we found that most of them follow this structure where code is in the beginning of the message. This would help in 2 things:

  1. The user can easily read the OTP from the notification without having to open the message
  2. If the project name is too large, it would be hard to read the OTP/ the message may exceed allowed characters of one message.

We can finalise the approach and I'll make the changes accordingly.

Copy link
Member

Choose a reason for hiding this comment

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

Okay I am fine with either messages as long as its detectable by the OS. Can we do a small test to trigger an SMS and check if the phone recognizes it?

Copy link
Member

@christyjacob4 christyjacob4 left a comment

Choose a reason for hiding this comment

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

Please address the comments.

@christyjacob4 christyjacob4 merged commit 9ff4a9d into 1.5.x Jan 12, 2024
21 checks passed
@stnguyen90 stnguyen90 deleted the fix-otp-template branch April 25, 2024 18:16
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.

None yet

2 participants