Skip to content

LG-305 Updated screen per design#2205

Merged
davemcorwin merged 3 commits intomasterfrom
LG-305-idv-phone-verification-screen
May 31, 2018
Merged

LG-305 Updated screen per design#2205
davemcorwin merged 3 commits intomasterfrom
LG-305-idv-phone-verification-screen

Conversation

@davemcorwin
Copy link
Copy Markdown
Contributor

screen shot 2018-05-29 at 2 33 15 pm

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_to in a controller, use _url, not _path.

  • When adding user data to the session, use the user_session helper
    instead of the session helper so the data does not persist beyond the user's
    session.

  • When adding a new controller that requires the user to be fully
    authenticated, make sure to add before_action :confirm_two_factor_authenticated.

- t('idv.messages.phone.rules').each do |msg|
li = msg

= simple_form_for(@view_model.idv_form, url: idv_phone_path,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its hard to tell in github, but is this nesting the form within the ul?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nope! but the diff view does make it look like it :)

screen shot 2018-05-30 at 6 24 39 am

unsupported_jurisdiction_sp: Please visit %{sp_name} to access your account.
form:
activate_by_mail: get a code by letter.
activate_by_mail: get a code via mail instead ›
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would consider inserting the > via CSS using :after rather than having it be part of the text string. I think it will be better for a11y, and also be more flexible if the preferred style were to change.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not opposed to it in concept, however, there is at least one other place where the guillemet is present and I was just going with the flow.

Originally, the one in English was different than Spanish and French, but per some the comment here, i changed them to be the same.

Copy link
Copy Markdown
Contributor

@stevegsa stevegsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@davemcorwin davemcorwin merged commit 890b892 into master May 31, 2018
@davemcorwin davemcorwin deleted the LG-305-idv-phone-verification-screen branch May 31, 2018 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants