Skip to content

LG-315 Can't submit personal key after typo#2215

Merged
stevegsa merged 1 commit intomasterfrom
stevegsa-fix-personal-key-submit-after-typo
Jun 6, 2018
Merged

LG-315 Can't submit personal key after typo#2215
stevegsa merged 1 commit intomasterfrom
stevegsa-fix-personal-key-submit-after-typo

Conversation

@stevegsa
Copy link
Contributor

@stevegsa stevegsa commented Jun 3, 2018

Why: When a user attempts to confirm a personal key and mistypes the key, they receive an error and the continue button is disabled.

How: Fix the logic for enabling/disabling the button and checking form validation upon user input. Rspec and Capybara are insufficient to test the javascript disabling/enabling of the submit button.

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.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think the bug here is that input.valid returns undefined. I think we're meaning to say input.checkValidity().

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was supposed to be validity.valid . Nice catch Hoops! I just assumed the form validation wasn't working and didn't look further.

Copy link
Contributor

@jmhooper jmhooper left a comment

Choose a reason for hiding this comment

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

Lookin good

**Why**: When a user attempts to confirm a personal key and mistypes the key, they receive an error and the continue button is disabled.

**How**: The logic for form validation is setting the input box to invalid after a bad key is entered and the form remains invalid even after changing the input (hence why the button stays disabled).  To have it behave as before we can simply remove the validation check that was added for enabling the button.
@stevegsa stevegsa force-pushed the stevegsa-fix-personal-key-submit-after-typo branch from 9f439cd to d1e7809 Compare June 6, 2018 20:45
@stevegsa stevegsa merged commit 288c56a into master Jun 6, 2018
@amathews-fs amathews-fs deleted the stevegsa-fix-personal-key-submit-after-typo branch January 7, 2021 18:36
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.

2 participants