-
Notifications
You must be signed in to change notification settings - Fork 24
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/resolve stats #883
Feat/resolve stats #883
Conversation
ciaranschutte
commented
Aug 14, 2024
•
edited
Loading
edited
- resolve network aggregation from multiple single network aggs
- Aggregations => NetworkAggregation
- unit tests
- not all properties covered, just the minimal buckets for now
@@ -1,2 +1,51 @@ | |||
import { SupportedAggregation, SUPPORTED_AGGREGATIONS } from '../common'; | |||
import { Aggregations, NetworkAggregation, NumericAggregations } from '../types'; | |||
|
|||
// TODO: implement | |||
export const resolveAggregations = (networkResults: void) => null; |
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.
When you get around to working on this function I'd update this name. I'd add something descriptive to distinguish it's purpose from resolveAggregation
@@ -0,0 +1,27 @@ | |||
import { resolveAggregation } from '..'; | |||
import { aggregation } from './fixture'; |
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.
Why fixture
, isn't stubs
the more common name for test data?