-
Notifications
You must be signed in to change notification settings - Fork 166
Remove idv/personal_key#download action #6162
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -179,6 +179,14 @@ def email_and_password_auth( | |
| ) | ||
| end | ||
|
|
||
| # @deprecated | ||
| # A user has downloaded their personal key. This event is no longer emitted. | ||
|
Comment on lines
+182
to
+183
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. YAGNI? Or is this just so that we have a reference in the analytics documentation for historical lookups?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I figured it would be good to have a reference. And if we choose to implement frontend logging, we can link these two as "previous event names" for that or something |
||
| # @identity.idp.event_name IdV: personal key downloaded | ||
| # @identity.idp.previous_event_name IdV: download personal key | ||
| def idv_personal_key_downloaded | ||
| track_event('IdV: personal key downloaded') | ||
| end | ||
|
|
||
| # @identity.idp.event_name IdV: phone confirmation otp submitted | ||
| # @param [Boolean] success | ||
| # @param [Hash] errors | ||
|
|
||
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.
🌶️ one downside to not having a server action is we no longer get the analytics
However, I still feel strongly enough that having this action on the server is a liability, so I am OK not having analytics if it means we can have a more bug-free frontend
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.
https://cm-jira.usa.gov/browse/LG-6111 so we can track this
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.
We have some precedent for front-end logging with #5875, which might be useful for this.
(Also commented as such on related ticket)