addressComponents and unresolvedTokens do not contain string offsets [308979484]

Assigned

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Nov 2, 2023 06:35PM

The addressComponents array is not returned in the order the components appear in the input (or output) address. This combined with the fact that the string offsets aren't included makes it very difficult to implement the suggested confirmation dialog UX. Additionally, unresolvedTokens should contain the string offsets as it's typical for tokens to appear multiple times.

Comments

ca...@google.com <ca...@google.com> Nov 3, 2023 03:44AM

Assigned to ca...@google.com.

ca...@google.com <ca...@google.com> #2Nov 3, 2023 06:18AM

Thank you for posting.

We are currently looking into this and will get back to you as soon as we have an update.

ca...@google.com <ca...@google.com> #3Nov 6, 2023 01:16AM

Reassigned to gm...@google.com.

Thanks for your suggestion!

We'll be reviewing this for further consideration. Please star this issue to get updates and leave comments for additional information. Please note that starring the issue also provides our product team with valuable feedback on the importance of the issue to our customers.

Issue 308979484

Description

Issue summary

Comments

ca...@google.com <ca...@google.com> Nov 3, 2023 03:44AM

ca...@google.com <ca...@google.com> #2Nov 3, 2023 06:18AM

ca...@google.com <ca...@google.com> #3Nov 6, 2023 01:16AM

Add comment

Issue metadata