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

Backend insights #19

Open
annevk opened this issue May 22, 2023 · 2 comments
Open

Backend insights #19

annevk opened this issue May 22, 2023 · 2 comments

Comments

@annevk
Copy link

annevk commented May 22, 2023

One thing that came out of the discussion is that actual shipping backends have a rather uniform way of writing down addresses. That would still be rather useful to know I think as perhaps that would allow us to simplify things overall.

@yoavweiss
Copy link

/cc @theindra

@theindra
Copy link

theindra commented May 8, 2024

I think generally this is true but there are some exceptions. Not related to shipping but most (all?) APIs for handling Brazil's e-invoicing laws deviate from the standard fields by splitting up an address_line1 into street_name and house_number which makes separation of the fields a defacto requirement in this country.
As a workaround most websites there disable autofill either for this field or for the entire form.

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

3 participants