#edgar-addresselement-errors
1 messages ยท Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- edgarsantiago93, 1 day ago, 10 messages
๐ @mortal isle do you have a bit more context to share?
sure! im testing address element with and without contacts, but im getting this errors
Can you share real text instead of pictures and the exact code
edgar-addresselement-errors
i understand i need to change things in the code but is there like a catch or onError that will handle this?
@mortal isle you might have missed my message/ask above
oh yeah sorry
so im trying to pass a value to the phone field in the form, this might be a dif qeustion, when i pass this value
return {
name: displayName || '',
address: {
line1: addressLine1,
city,
state,
postal_code: zip,
country,
},
phone:'+527333532826'
};
i get this
i havent been able to find a phone format in the docs
the errors you are getting are not related to the format though
I don't think we offer a way to "catch" those
The idea here is that you as the developer made an integration mistake so we don't offer a way to catch those
ah gotcha
i see, that makes sense ๐
so regarding the format, is there a "standardized" way of passing the phone vlaue?
the best approach is with the country code
but in my example i passed the full number (valid in mexico, 10 digits plus country code) and although the country code did get set correctly, the valueis the full string (including country code)
it works fine for me locally
'address',
{
mode: 'billing',
defaultValues: {
phone: '+527333532826',
},
fields: {
phone: 'always',
},
}
);```
Does ^ work?
testing
lol