LG 304 idv phone confirmation screen#2206
Merged
davemcorwin merged 6 commits intomasterfrom May 31, 2018
Merged
Conversation
jmhooper
reviewed
May 30, 2018
| def confirm_idv_steps_complete | ||
| return redirect_to(idv_session_url) unless idv_profile_complete? | ||
| return redirect_to(idv_address_url) unless idv_address_complete? | ||
| return redirect_to(idv_phone_url) unless idv_address_complete? |
Contributor
There was a problem hiding this comment.
Does it still make sense to use idv_address_complete? here? That looks like something we could tear out of Idv::Session now.
Contributor
Author
There was a problem hiding this comment.
idv_address_complete? is defined in that controller:
def idv_address_complete?
idv_session.address_mechanism_chosen?
end
I left it and didn't rename it because:
- we're still kinda sorta verifying address here
- the address mechanism is still important, it gets set when phone/usps verification is actually done and I didn't want to remove it.
- didn't want the PR to start ballooning, but if we should move or remove it, I can do that in a separate PR.
Contributor
There was a problem hiding this comment.
👍. Let's just keep in mind that address method selection looks like a good place to start an Idv::Session refactor if somehow we ever get bored.
jmhooper
approved these changes
May 31, 2018
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes the 'address' step, dropping the user on the phone verification screen immediately after identity resolution (session#create). The promotes the idea that the happy path is using phone to verify address, but there is still a link to use mail if necessary.
No cosmetic changes are here, those are in #2205
Hi! Before submitting your PR for review, and/or before merging it, please
go through the following checklist:
For DB changes, check for missing indexes, check to see if the changes
affect other apps (such as the dashboard), make sure the DB columns in the
various environments are properly populated, coordinate with devops, plan
migrations in separate steps.
For route changes, make sure GET requests don't change state or result in
destructive behavior. GET requests should only result in information being
read, not written.
For encryption changes, make sure it is compatible with data that was
encrypted with the old code.
For secrets changes, make sure to update the S3 secrets bucket with the
new configs in all environments.
Do not disable Rubocop or Reek offenses unless you are absolutely sure
they are false positives. If you're not sure how to fix the offense, please
ask a teammate.
When reading data, write tests for nil values, empty strings,
and invalid formats.
When calling
redirect_toin a controller, use_url, not_path.When adding user data to the session, use the
user_sessionhelperinstead of the
sessionhelper so the data does not persist beyond the user'ssession.
When adding a new controller that requires the user to be fully
authenticated, make sure to add
before_action :confirm_two_factor_authenticated.