-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-11329] [chore] Add "otp" TotpFieldNames array in autofill-constants.ts #10717
Conversation
Add "otp" TotpFieldNames array in autofill-constants.ts. Noticed on https://id.fedoraproject.org/login/
Thank you for your contribution! We've added this to our internal Community PR board for review. |
There was a problem hiding this 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; thanks for the contribution! Our QA team will take a look next and assuming that all goes well, we'll be able to merge this in. 👍
A note: because of how we currently match against these constants, there can be unintended matching against coincidental (but unintended) values. We're aware of this and working on improving those strategies to mitigate that possibility.
New Issues
Fixed Issues
|
Great! Thank you. |
Thanks again for your work here, @mulderje This work has completed our QA process and I've merged it to the |
Add "otp" TotpFieldNames array in autofill-constants.ts. Noticed on https://id.fedoraproject.org/login/
🎟️ Tracking
N/A
📔 Objective
Add "otp" TotpFieldNames array in autofill-constants.ts. Noticed on https://id.fedoraproject.org/login/
As an aside, has a custom "linked" field been considered here like with passwords? I noticed at least one request on the forum, but couldn't find much here with a search.
📸 Screenshots
N/A
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes