LG-9139: Support double address verification on address page#8041
LG-9139: Support double address verification on address page#8041eileen-nava merged 12 commits intomainfrom
Conversation
|
|
||
| def call | ||
| Idv::InPerson::AddressForm::ATTRIBUTES.each do |attr| | ||
| if attr == :same_address_as_id && IdentityConfig.store. |
There was a problem hiding this comment.
checking my understanding - here we're saying if the current residential address is the same as the one on the user's id don't get attributes from flow_params
There was a problem hiding this comment.
No, we're choosing whether to assign the same_address_as_id field to the session here based on the feature flag. #call here is accepting data from the address form submission.
|
I reran the failed spec to make sure, and the same test failed twice. The failed test suggests that this PR may have introduced a regression or test issue related to analytics. |
spec/features/idv/in_person_spec.rb
Outdated
| search_for_post_office | ||
|
|
||
| # location page | ||
| location = page.find_all('.location-collection-item')[1] |
There was a problem hiding this comment.
Test has been updated to use a more stable version of this step.
| increment_step_name_counts | ||
| analytics.public_send( | ||
| flow.step_handler(step).analytics_submitted_event, | ||
| flow.step_handler_instance(step).analytics_submitted_event, |
There was a problem hiding this comment.
we should probably add a ticket to revisit this when the flow state machine is removed
svalexander
left a comment
There was a problem hiding this comment.
LGTM. There was a failing test ( didn't seem related to these changes though) but when I re-ran it all the specs passed.
|
|
||
| attr_accessor(*ATTRIBUTES) | ||
|
|
||
| attr_reader :capture_secondary_id_enabled |
There was a problem hiding this comment.
WDYT of removing this and making a nice ? method instead?
| attr_reader :capture_secondary_id_enabled | |
| def capture_secondary_id_enabled? | |
| @capture_secondary_id_enabled | |
| end |
There was a problem hiding this comment.
Alternatively, we use this pattern in a few places to achieve the same effect:
identity-idp/app/presenters/session_timeout_modal_presenter.rb
Lines 16 to 17 in fb439d8
| increment_step_name_counts | ||
| analytics.public_send( | ||
| flow.step_handler(step).analytics_submitted_event, | ||
| flow.step_handler_instance(step).analytics_submitted_event, |
| before do | ||
| allow(IdentityConfig.store).to receive(:in_person_proofing_enabled).and_return(true) | ||
| allow(IdentityConfig.store).to receive(:in_person_proofing_enabled).and_return(false) | ||
| allow(IdentityConfig.store).to receive(:in_person_capture_secondary_id_enabled). |
There was a problem hiding this comment.
Thank you for catching this! 🙏🏻
🎫 Ticket
LG-9139: Updates to Address page for Double Address Verification
🛠 Summary of changes
For all users...
Display beginning implementation of hint text for Puerto Rico userscovered by LG-9200 (out of scope)When the feature flag is true....
Note about technical changes:
BaseStepinstances in addition to the singleton methods on the classes. This supports validation based on user attributes, and one of the included feature tests will fail if the validation is instead added/removed statically.📜 Testing Plan
High-level steps
Detailed testing steps
Feature Flag - Off
in_person_capture_secondary_id_enabledin_person_capture_secondary_id_enabledFeature Flag - On
in_person_capture_secondary_id_enabledin_person_capture_secondary_id_enabled👀 Screenshots
If relevant, include a screenshot or screen capture of the changes.
English:
Spanish:
French: