Skip to content

[HOLD for payment 2022-05-20][$1000] - Audit forms and fix inconsistencies with modifying user input #7524

Closed

Description

@luacmartins

We should audit all our forms and fix any inconsistencies with modifying user input. The expected behavior is as follows:

  1. User input should not be modified as they type.
  2. User input that may include optional characters (e.g. (, ), - in a phone number) and should never be restricted on input, nor be modified or formatted on blur.
  3. Instead we will format and clean the user input internally before using the value (e.g. making an API request where the user will never see this transformation happen)
  4. Additionally, users should always be able to copy/paste whatever characters they want into fields.

To give a slightly more detailed example of how this would work with phone numbers we should:

  • Allow any character to be entered in the field.
  • On blur, strip all non-number characters (with the exception of + if the API accepts it) and validate the result against the E.164 regex pattern we use for a valid phone. Stripping characters should happen internally and result in NO UI change to the user.
  • On submit, repeat validation and submit with the clean value.

Here's a list of forms to be audited:

Activity

  1. MelvinBot commented on Feb 2, 2022

    @MelvinBot
    Contributor

    Triggered auto assignment to @SofiedeVreese (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

  2. luacmartins commented on Feb 2, 2022

    @luacmartins
    ContributorAuthor

    Actually, we might use Applause to do this audit for us. Removing the External label.

  3. removed
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 2, 2022
  4. MelvinBot commented on Feb 15, 2022

    @MelvinBot
    Contributor

    12 days overdue now... This issue's end is nigh!

  5. MelvinBot commented on Feb 15, 2022

    @MelvinBot
    Contributor

    12 days overdue. Walking. Toward. The. Light...

  6. luacmartins commented on Feb 15, 2022

    @luacmartins
    ContributorAuthor

    Nvm my previous comment, this can be handled by contributors! Adding External label.

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 15, 2022
  8. 99 remaining items

  9. luacmartins commented on May 2, 2022

    @luacmartins
    ContributorAuthor

    @JmillsExpensify as per this comment, there should be 4x $250 milestones for this job, for a total of $1000. As of now, 3/4 milestones have been completed ($750).

    @eVoloshchak when do you think you can complete the last 4 audits?

  10. eVoloshchak commented on May 2, 2022

    @eVoloshchak
    Contributor

    @eVoloshchak when do you think you can complete the last 4 audits?

    I already did that, both PR's are merged, the latest one will soon be deployed to production

  11. luacmartins commented on May 2, 2022

    @luacmartins
    ContributorAuthor

    Ah nice! Thanks for linking that last PR!

    Ok, so 3 milestones are complete and should be paid. The last one is waiting on this PR being deployed and the 7 day regression period.

  12. mallenexpensify commented on May 4, 2022

    @mallenexpensify
    Contributor

    @eVoloshchak paid 3 milestones totaling $750 (I'm not sure if the one's finished are aligned with the ones paid in Upwork but the total amounts will wash out).

    cc @JmillsExpensify since you'll likely be the one issuing the final $250 payment 7 days after #8764 hits production (if no regressions)

  13. JmillsExpensify commented on May 5, 2022

    @JmillsExpensify
    Contributor

    Awesome, thanks! Looks like we're still waiting on that last PR to hit production (and confirm no regressions).

  14. JmillsExpensify commented on May 10, 2022

    @JmillsExpensify
    Contributor

    PR hit staging yesterday.

  15. changed the title [-][$1000] - Audit forms and fix inconsistencies with modifying user input[/-] [+][HOLD for payment 2022-05-20][$1000] - Audit forms and fix inconsistencies with modifying user input[/+] on May 17, 2022
  16. JmillsExpensify commented on May 17, 2022

    @JmillsExpensify
    Contributor

    A couple more days left on the 7-day hold for that last PR.

  17. JmillsExpensify commented on May 23, 2022

    @JmillsExpensify
    Contributor

    Jumping in to process this one now and pay outstanding contributors.

  18. JmillsExpensify commented on May 23, 2022

    @JmillsExpensify
    Contributor

    Got a little confused on the payments, but after re-adding the above I'll be issuing the final $250 payment. @rushatgabhane I've also closed out your C+ contract.

    @luacmartins Can we also close out this ensure issue now?

  19. luacmartins commented on May 23, 2022

    @luacmartins
    ContributorAuthor

    @JmillsExpensify Yes! This was the last payment so I believe that all milestones have been paid out. Thanks for working on this!

  20. parasharrajat commented on May 24, 2022

    @parasharrajat
    Member

    Shouldn't this be convered as part of this issue?

  21. luacmartins commented on May 24, 2022

    @luacmartins
    ContributorAuthor

    Hmm that seems to be out of scope for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionEngineeringExternalAdded to denote the issue can be worked on by a contributorTaskWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions