We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, for each tx, we have no info regarding what this tx does, the tx id, and how long this tx is expecting to be processed.
If we have multiple tx for one operation, e.g. (approve then apply), we have no info shown to users between each tx.
It will be great to have a wizard to which guides users to go through a list of transactions.
We'd like such wizard to be general purpose, and provide the following functionalities:
Input: [ list of tx descriptions]
tx description = [ description of the tx, callback() which initiates a tx]
UI: The wizard behaves like a popup, we have one page for each tx, and a "continue" button to go to the next tx.
For each tx, we would like to have the following info:
If you have any other ideas, please let me know.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, for each tx, we have no info regarding what this tx does, the tx id, and how long this tx is expecting to be processed.
If we have multiple tx for one operation, e.g. (approve then apply), we have no info shown to users between each tx.
It will be great to have a wizard to which guides users to go through a list of transactions.
We'd like such wizard to be general purpose, and provide the following functionalities:
Input: [ list of tx descriptions]
tx description = [ description of the tx, callback() which initiates a tx]
UI:
The wizard behaves like a popup, we have one page for each tx, and a "continue" button to go to the next tx.
For each tx, we would like to have the following info:
If you have any other ideas, please let me know.
The text was updated successfully, but these errors were encountered: