This repository was archived by the owner on Sep 15, 2025. It is now read-only.
Fetching time-series data: architecture #95
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
Contributor
Because.... no one does that. 😉 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This is a counterpart to the Insights fetching — handling data that's tied to specific time intervals.
This PR is meant mostly to show how I'm planning to tackle it architecturally — there are only two classes so far — more to come in future PRs tomorrow.
one caveat: the naming in this PR is atrocious. I want to change every single class name I introduce here, but I couldn't come up with anything better on the spot, and I didn't want to bang my head against the wall for few hours just trying to come up with better names. I promise I'll rename it before I'm done with all of the networking.
Testing Details