Closed dennis00010011b closed 5 years ago
I need confirmation for the approach that I'll be taking on this issue, as at some point it will require the user interaction.
Each step of the deployment process has a list of actions, to make it the most grained possible this can be divided into 4 different actions:
If I treat each one of those actions as a flag, TW will require user interaction for the step .2
. In this case, the TW can prompt the user to cancel the current Tx pending of approval in the wallet and hit a Continue button, which will trigger the step to be re-sent.
For the step .3
there'll TW will track the pending transaction by its transactionHash
, and will continue without the user noticing it. Maybe, in this step, we can prompt the user with a message or highlight the step for the tx pending of being mined.
@dennis00010011b @vbaranov thoghts?
I agree, that 2.
step cannot be resolved without interaction with a user. I support prompting in this case.
As for the statuses of tx life cycle, maybe we could show 1-3 statuses to a user by means of labels for every current pending tx, like this (I do not pretend to exact styles, but something like this):
Thereby, a user will see what is the current status of pending tx. So, in case of refreshing at 3.
step he/she will see again tx is pending of being mined...
(without prompting) and after inclusion tx to the block, we move to the next tx. @fernandomg @dennis00010011b - it is open for discussion.
Steps:
Expected result:
Actual result:
If you are reporting a problem with Token Wizard, please include the following information:
Which network did you use? (Mainnet, Kovan, Rinkeby, etc.)
any
If you were able to create it, what is the URL of your crowdsale?
n/a
Do you have screenshots showing the problem?
Do you see errors in the dev console? If yes, please include a screenshot
No