Skip to content
This repository has been archived by the owner on Dec 2, 2021. It is now read-only.

Need address entry #70

Open
embreinhardt opened this issue Apr 22, 2020 · 1 comment
Open

Need address entry #70

embreinhardt opened this issue Apr 22, 2020 · 1 comment
Assignees

Comments

@embreinhardt
Copy link
Contributor

Either typeahead (ideal), or split fields for address, address2, city, state, zip

Screen Shot 2020-04-21 at 8 56 32 PM

@mchin-cca
Copy link
Contributor

The recommendation is to integrate an address look up service like Loqate, and then default to separate fields as a backup.

colinking added a commit that referenced this issue Apr 28, 2020
This PR adds client-side validation and formatting for:
- Integers: resolves #73)
- Decimals: resolves #73
- Dollar Amounts: resolves #73 (however, this will need an update after #77)
- shorttext + longtext
- date: resolves #69 (w/ new `min` and `max` validation fields)
- dropdown + singleselect
- multi-select
- boolean
- phone: resolves #15
- ssn: resolves #16
- state picker
- instructions-only
- arn

Some examples:

![image](https://user-images.githubusercontent.com/2907397/80447063-3f4e7100-88cd-11ea-974d-e0b51099e639.png)

![image](https://user-images.githubusercontent.com/2907397/80447072-44abbb80-88cd-11ea-9544-c6b86a9193ac.png)

It also cleans up some of the submission types (booleans submit as booleans not strings; phone numbers are integers; etc.).

It also adds regression testing, based on Alex's work, to the client for this validation.

After this PR, we'll still need validation for:
- address fields, but that's pending an update to how addresses are recorded with: #70
- files when that ships
- driver's licenses, depending on DL formats #72
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants