Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Prune data #36
Prune data #36
Changes from all commits
0ada41d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 the timestamp include the unit in the name? Or should it rather be a
Date
and the function handles converting to a Unix timestamp internally?It's not obvious to me if "maxIgnoreAfterTimestamp" is in seconds or milliseconds and requires me to dig through several other functions to figure this out.
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.
Timestamp should imo always refer to unix timestamp and thus be in seconds. We also use this implicitly for signed data currently (e.g. the input for the signed API expects the timestamp
signed-api/packages/api/src/schema.ts
Line 45 in 044a9d7
Also, my intention is for the cache to work with timestamps and not delays. That's why I made API handlers convert the required delay to timestamp before calling the cache functions.
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.
"data" is already the plural form 😛 "datum" is the singular
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.
Yeah, but we always use
data
in singular and then there is the dillemma how to call a "group" of data. After a bit of internal pain, the "datas" was the best I could come up with. Calling itallSignedDataArray
was second on my internal list afair. Do you like more?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.
I guess it's fine as is. Not sure how I feel about the alternative
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.
I also find
datas
useful (specificallycalldatas
in a multicall situation) but then https://github.com/api3dao/manager-multisig/pull/213#discussion_r1284344567