You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue with Google autocomplete on Places API is
if we search without a 'street number', API will return partial addresses (e.g. no street number, no zip too IIRC)
if we search with a 'street number', we can get a full address, then store directly.
Another issue is determining if complete addresses can start without a number (e.g. PO box, if we store those)
if we do store addresses that start without a number, we could
make another form and fields for those edge cases (e.g. user checks PO box checkbox, and we show a different form)
backend-validate response contains all fields.. this could mean we have a 'complete address'
if we only store addresses that start with a number, we can
frontend-validate query on starts with a number, then store response directly as DomesticAddress model
After a cursory search, I believe complete addresses need a street number. Whether or not 'street numbers' can start with a letter is another concern.
The text was updated successfully, but these errors were encountered:
The issue with Google autocomplete on Places API is
if we search without a 'street number', API will return partial addresses (e.g. no street number, no zip too IIRC)
if we search with a 'street number', we can get a full address, then store directly.
Another issue is determining if complete addresses can start without a number (e.g. PO box, if we store those)
if we do store addresses that start without a number, we could
if we only store addresses that start with a number, we can
After a cursory search, I believe complete addresses need a street number. Whether or not 'street numbers' can start with a letter is another concern.
The text was updated successfully, but these errors were encountered: