-
Notifications
You must be signed in to change notification settings - Fork 4
feat: add lastUpdated timestamp to all OO subgraphs, so we can use this when querying #99
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
base: master
Are you sure you want to change the base?
Conversation
…is when querying Signed-off-by: Matt Rice <[email protected]>
md0x
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.
Looks good. Just a minor comment.
gsteenkamp89
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.
One nit, but looks good!
|
|
||
| eventBased: Boolean | ||
|
|
||
| lastUpdated: BigInt |
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.
We could make these non-nullible, if we intialize with BIGINT_ZERO like we do in getOrCreateOptimisticPriceRequest
| lastUpdated: BigInt | |
| lastUpdated: BigInt! |
| request.currency = Bytes.fromI32(0); | ||
| request.reward = BIGINT_ZERO; | ||
| request.finalFee = BIGINT_ZERO; | ||
| request.lastUpdated = BIGINT_ZERO; |
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.
Should we init the rest of the packages to Big_int zero for consistency? Or can we drop it since lastUpdate gets set on every PriceRequested event?
No description provided.