-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feat: Included API handling for fetching from daily_node_metrics #71
Feat: Included API handling for fetching from daily_node_metrics #71
Conversation
ba22be4
to
1d9f34b
Compare
1d9f34b
to
a9e60ed
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.
I feel it's important to structure the code implementing these "platform stats" endpoints so that it's easy to mirror future updates from spark-stats to voyager-stats repo.
Let's follow the approach we used in CheckerNetwork/spark-evaluate#188.
I.e. there should be two new files - one for the production code and one for the tests - that can be copied as-is from spark-stats to voyager-stats to mirror the changes.
I need to update this PR to reflect the change from 'metric_date' to 'day' in CheckerNetwork/spark-evaluate#188 |
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.
The pull request looks pretty good now! I have a few minor comments to address, PTAL.
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 think we need to wait until CheckerNetwork/spark-evaluate#188 is landed and Dependabot updates the dependency in package.json
, to get the new DB schema migration scripts that will create the new daily_stations
table.
Links:
CheckerNetwork/roadmap#96