-
Notifications
You must be signed in to change notification settings - Fork 20
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
P-397 Add the new VC test case for ts-tests. #2537
Conversation
0861fad
to
6d7a943
Compare
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.
Overall looks good for me. Just one question came to my mind, what are the reasons to hardcode some paths within data providers like "v1/blocks/e4068e6a326243468f35dcdc0c43f686/children". Is the e406....f686
identifier permanent, or it might change in some cases?
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
I think it's simply moving around the hard code place. |
Context
resolves p-397
Now all vc basic tests(e.g.
di_vc
,dr_vc
,ii_vc
tests) get data from mock service, and real data-provider tests are not included in this test.I have modified some rust code, please help to take a closer look, I hope it will not affect worker logic.