-
Notifications
You must be signed in to change notification settings - Fork 5
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
Initial update conditions checking #39
Conversation
I agree. |
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 see that this PR is failing the tests. How come you were able to merge it? 👀 |
I realized these https://github.com/api3dao/airseeker-v2/blob/main/.github/workflows/main.yml#L54 is the cause. We have different strategy for running tests in airseeker then we have in Airnode (which is fine imo). |
This is largely a copy of the update conditions check in Airseeker v1 (why change something that works well?). I had to add some extra code due to
"noUncheckedIndexedAccess": true,
intsconfig.js
and our stringent eslint rules.An alternative to ethers' BigNumber is to use BigNumber.js, which can handle floating point big numbers - it works nicely in Airseeker Telemetry and it's easier to think about.
Closes #18