-
Notifications
You must be signed in to change notification settings - Fork 166
LG-9865: Add same_address_as_id to in person verify visited analytics #8585
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
3c4a185
add same_address_as_id to verify visited analytics
gina-yamada 0d6edd6
mark in person verify info set as complete
gina-yamada 52731f9
changelog: Interal, In-person proofing, Add same_address_as_id to in …
gina-yamada 0f3c14c
Moved setting value on flow session to verify info concern
gina-yamada d825718
Merge branch 'main' of github.com:18F/identity-idp into gyamada/fix-v…
gina-yamada 3bcdc04
Update app/controllers/concerns/idv/verify_info_concern.rb
gina-yamada b41acd5
Modified how I was accessing data for readability
gina-yamada File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,7 +3,7 @@ | |
| RSpec.describe Idv::InPerson::VerifyInfoController do | ||
| include IdvHelper | ||
|
|
||
| let(:pii_from_user) { Idp::Constants::MOCK_IDV_APPLICANT_WITH_SSN.dup } | ||
| let(:pii_from_user) { Idp::Constants::MOCK_IDV_APPLICANT_SAME_ADDRESS_AS_ID.dup } | ||
| let(:flow_session) do | ||
| { 'document_capture_session_uuid' => 'fd14e181-6fb1-4cdc-92e0-ef66dad0df4e', | ||
| :pii_from_user => pii_from_user, | ||
|
|
@@ -67,6 +67,8 @@ | |
| flow_path: 'standard', | ||
| irs_reproofing: false, | ||
| step: 'verify', | ||
| same_address_as_id: true, | ||
| pii_like_keypaths: [[:same_address_as_id], [:state_id, :state_id_jurisdiction]], | ||
|
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. I just checked, and the first thing Analytics#track_events does is |
||
| } | ||
| end | ||
|
|
||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Just curious, but why are we coercing to a string here? Do we not know the type of :same_address_as_id?
In the spec it's a boolean, so if that's the case then you shouldn't have to coerce the type or compare the value.
Uh oh!
There was an error while loading. Please reload this page.
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.
@JackRyan1989 This bit of code was taken from in_person_flow.rb, I kept it the exact same as is it just missing on analytics when moving verify out of the flow state machine (discovered in the delete PR). There is a ticket, LG-9543, to refactor all string instances of same_address_as_id to a boolean because both are being used. That ticket was started but presented roadblocks. How do you feel about that being handled in ticket LG-9543?
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.
Sounds good!
Super nit: Maybe change the "same_address_as_id" to be a string in the test then? This is not a blocking comment.
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.
This is not needed. Analytic data is a boolean. @JackRyan1989 and I jumped on a call.