-
Notifications
You must be signed in to change notification settings - Fork 28
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
add pagination for List, move executions list to its own endpoint #53
Conversation
3d4ed39
to
dfb40e4
Compare
dfb40e4
to
851636e
Compare
@@ -0,0 +1,85 @@ | |||
syntax = "proto3"; |
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.
Split node defininiton into its own proto file . This way for node update there won't be any change to the SDK
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.
Looks good to me.
One question is that, how should we generate executions data in sdk tests? We can set the block interval to 1 and wait for a few blocks to get the executions result?
Hi @v9n, is it possible to get the total number of ListTasks? The |
Another thought: I think it would be better to standardize the response format of both calls. Personally, I prefer the format of getExecutions, which is:
|
yes, we can return the total in this as well.
did you check the protocolbuf, they had standarize to the same |
Fixes #43 #44 #45
List Task
Then we can oad more by passing the cursor.
Returns
List Executions