Skip to content

Conversation

@xsats
Copy link
Contributor

@xsats xsats commented Sep 21, 2022

No description provided.

Copy link
Member

@tanx tanx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made one comment. Also looks like the package-lock.json is conflicting after merging the other PR to the master.

return nextFreeAddresses;
}
// return object: [{ index: "", address: ""}, ...]

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this different from async getAddressAsync() right above it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function returns n addresses starting from the next unused address retrieved by getAddressAsync(). I suppose the looping could just happen on the app side but I think it's a useful minor addition to the library.

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

Successfully merging this pull request may close these issues.

2 participants