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
Is your feature request related to a problem? Please describe.
We do some geocoding in our app that requires that we can actually look up the fake addresses we generate, and our db fields are separated into street, city, zip etc. We could probably parse the full_address response, but would be better to have a real fake address that we could geocode against with separate fields for pulling parts out.
If you're adding new objects, please describe how you would use them
Just have Faker::Address.full_address_hash or full_address_object so we can easily pull parts out. And have them be "real", at least for city, zip, pairs.
Describe alternatives you've considered
Parsing the existing full_address
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We do some geocoding in our app that requires that we can actually look up the fake addresses we generate, and our db fields are separated into street, city, zip etc. We could probably parse the full_address response, but would be better to have a real fake address that we could geocode against with separate fields for pulling parts out.
If you're adding new objects, please describe how you would use them
Just have Faker::Address.full_address_hash or full_address_object so we can easily pull parts out. And have them be "real", at least for city, zip, pairs.
Describe alternatives you've considered
Parsing the existing full_address
Additional context
The text was updated successfully, but these errors were encountered: