Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using # as secondary designator results in inconsistent behavior #32

Open
bluenike opened this issue Apr 20, 2020 · 0 comments
Open

Using # as secondary designator results in inconsistent behavior #32

bluenike opened this issue Apr 20, 2020 · 0 comments

Comments

@bluenike
Copy link

We have an html input for address entry. We use Google Maps Autocomplete to provide suggestions. Google Maps doesn't handle secondary designators very well during interactive input, so we use parse-address to remove the secondary designator. For this reason, it's important that parse-address acts consistently with partial input (as the user is typing).

Input: "10 miller pl Unit 505, san fran"
Output: {"number":"10","street":"miller","type":"Pl","sec_unit_type":"Unit","sec_unit_num":"505"}
Comment: Correctly identifies secondary information as "Unit 505"

However--

Input: "10 miller pl #505, san fran"
Output: {"number":"10","street":"miller","type":"Pl"}
Comment: Does not correctly identify secondary information as "#505" until the entire address is completely entered.

Input: "10 miller pl #505, san francisco, ca"
Output: {"number":"10","street":"miller","type":"Pl","sec_unit_type":"Unit","sec_unit_num":"505"}
Comment: Correctly identifies all components.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant