-
Notifications
You must be signed in to change notification settings - Fork 60
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
refactor(store): HistoryQuery.direction #2263
Conversation
You can find the image built from this PR at
Built from f8677e4 |
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.
Thanks for this PR!
It looks great! Besides, I think it would be a bit better if we could use the following type when we refer to a "pagination direction", if that's feasible of course
Line 44 in 103d398
PagingDirectionRPC* {.pure.} = enum |
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! Thanks! Just added a minor comment
61d9e29
to
4b32cf4
Compare
…ons: Should use the same value.
1ca30ae
to
01214b1
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.
It is great, thank you. I realized how rest and rpc namings are differ but its not an issue to change. We will remove sometime rpc thus we should not break any interface just because of it.
* Fix issue with default history query ascending value in serde operations: Should use the same value. * Update direction types to PagingDirection.
Description
Update
HistoryQuery.ascending
(and related) references todirection
so they are consistent with RFC naming. Also, fix a default value issue with it.Changes
ascending
references todirection
HistoryQuery.direction