-
Notifications
You must be signed in to change notification settings - Fork 215
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
(Feature) Give user information about crowdsale deployment status and provide the ability to resume #464
Comments
@fernandomg I think using something like |
Don't we have localStorage with MobX? |
@rstormsf yes, it's really useful. I'll add it in a different stage, as it has to be thoroughly tested. To avoid persisting undesired information across sessions (maybe https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage is the best option for this phase). @igorbarinov I don't think that persistence is part of the Mobx core. |
This feature is already done, the part related to localStorage will be worked as part of #529 |
Due to the recent issues we were facing with the crowdsale deployment, I think that will be a good idea to add an informative list with each step and its status in
stepFour
i.e.:
Also, add the ability to resume from where the process was halted.
Thus, if the user don't leave the screen or refresh it; he/she will be able to continue from where the deployment failed if for instance the Tx goes OOG, Metamask fails for any reason, and that kind of issues.
@igorbarinov @vbaranov l look forward to your comments.
The text was updated successfully, but these errors were encountered: