Skip to content

Lack of support to sequenced RPC requests #551

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

Closed
alexruzenhack opened this issue Sep 4, 2024 · 1 comment
Closed

Lack of support to sequenced RPC requests #551

alexruzenhack opened this issue Sep 4, 2024 · 1 comment
Assignees

Comments

@alexruzenhack
Copy link
Contributor

@andreabadesso has found that the success feedback after RPC request approval doesn't allow the handling of two RPC requests in sequence, once the dismiss of the feedback sends the user back to dashboard and dismiss the possibility of other request.

@alexruzenhack alexruzenhack added the bug Something isn't working label Sep 4, 2024
@alexruzenhack alexruzenhack self-assigned this Sep 4, 2024
@alexruzenhack alexruzenhack moved this from Todo to In Progress (WIP) in Hathor Network Sep 4, 2024
@alexruzenhack alexruzenhack removed the bug Something isn't working label Sep 5, 2024
@alexruzenhack
Copy link
Contributor Author

It is not a lack of support, actually the success feedback modal can remains active if user doesn't act on it, meanwhile a new nano contract request can happen, the screen will load the information for this new request in the background and the success feedback modal will keep active.

A quick solution was to create a screen for the success feedback, see the PR: #554. But we should refactor the handling of new nano contract transaction request to create a queue and let the user manage it.

@github-project-automation github-project-automation bot moved this from In Review (Done) to Waiting to be deployed in Hathor Network Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant