-
Notifications
You must be signed in to change notification settings - Fork 403
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
Bako ID integration #1180
base: master
Are you sure you want to change the base?
Bako ID integration #1180
Conversation
if (!name && isReceiver) { | ||
resolveAddressName(); | ||
} | ||
|
||
if (!isReceiver) { | ||
setAccountName(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added it only to show in the receiver, thinking about the transaction sending flow, what do you think?
If they're not a receiver, there could be a conflict with the wallet name.
const Name = !name ? ( | ||
<ContentLoader width={100} height={17} viewBox="0 0 80 17"> | ||
<ContentLoader.Rect x="0" y="0" width="100" height="17" rx="4" /> | ||
</ContentLoader> | ||
) : ( | ||
`${name}` | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a loader to the name to avoid screen flickering when the search is completed.
This feature enables sending a transaction by handles in Bako, handle is
@
with a identifier name, an example:@fuel_network
👇Check Bako ID docs
Changes:
Bech32
or@bako_handle
resolver
address@bako-id/sdk@0.0.6
package