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
I'm using an address field but need my regions to all be consistent.
This is tough since there's no validation on the field.
Ideally it would be a dropdown of US state, Canadian Provinces, etc. based on the country - but that obviously get tough to scale to other countries.
Maybe an easy alternative would be a fieldtype option where you could optionally define a regex pattern for each sub-field (postal code, region, etc) to validate against. Then at least you could enforce, e.g. ISO 3166-2
The text was updated successfully, but these errors were encountered:
Hey Tim, I am very sorry I missed this when you first posted it. I was traveling at the time, and must have mis-filed the notification email. At the moment, I think the additional UI complexity of field-by-field regex validation is probably going to be such that I won't add it right now. I will definitely think on this though, and see if I can come up with some elegant solution to the validation problem. Dealing with international addresses is quite a pain, as it turns out!
I'm using an address field but need my regions to all be consistent.
This is tough since there's no validation on the field.
Ideally it would be a dropdown of US state, Canadian Provinces, etc. based on the country - but that obviously get tough to scale to other countries.
Maybe an easy alternative would be a fieldtype option where you could optionally define a regex pattern for each sub-field (postal code, region, etc) to validate against. Then at least you could enforce, e.g. ISO 3166-2
The text was updated successfully, but these errors were encountered: