-
Notifications
You must be signed in to change notification settings - Fork 26
feat: test scenarios for visualization tool #409
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
feat: test scenarios for visualization tool #409
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
9f99e7f to
7c0d5cd
Compare
|
@tuler , The only thing that will be missing based on the cases for now is the |
|
@tuler, I will be marking this PR as ready for review as I believe the next steps would be starting adding access to portals, then voucher execution and so on. |
tuler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary
code changes to display test scenarios for the visualization tool as described in issue #400 based on available data structures provided by rollups-node json-rpc-api. The mocked data lies in the middleware thus providing the expected responses as we don't have a general rollups-node running. Currently, It is enabled based on environment variables.