Skip to content
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

Allow Node library users to have full control over the transaction lifecycle #93

Open
psiemens opened this issue Sep 19, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@psiemens
Copy link
Contributor

psiemens commented Sep 19, 2022

Currently a user can call client.sendAsync, which submits a transaction to Flow and return its transaction ID. They can then poll for the results of that transaction by ID. However, they will need to parse any errors and events themselves, rather than relying on the built-in handlers inside Freshmint.

Some users will need to manage the complete lifecycle of a transaction in order to remain fault tolerant and respond to errors gracefully. We should find a way for the caller to own the transaction lifecycle but still make use of the event parsing functions provided by Freshmint.

@psiemens psiemens added the enhancement New feature or request label Sep 19, 2022
@psiemens psiemens self-assigned this Sep 19, 2022
@psiemens
Copy link
Contributor Author

Note: this probably also means improving the error handling logic here: https://github.com/packagelabs/freshmint/blob/alpha/src/lib/transactions.ts#L105

Callers should be able to distinguish between network errors and execution errors, for example, and handle them accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant