-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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(trends): Added smoothing to new trends query runner #19578
Conversation
Hey @Gilbert09! 👋 |
and self.query.trendsFilter.smoothing_intervals is not None | ||
and self.query.trendsFilter.smoothing_intervals > 1 | ||
): | ||
smoothing_count = ast.Alias( |
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 would love if we switched the vague "smoothing" terminology to "rolling average". This was a UI issue we saw with some of the users we opted into this beta feature. In the code this is not so much as UX issue, but still worth having a single accurate name (except smoothing_intervals
I guess, since that's an existing schema)
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.
Nice yeah, have updated this
* Added smoothing to new trends query runner * Update query snapshots * Update query snapshots * Fixed tests * Update query snapshots * Updated the name to rolling average * Fixed snaoshots * Update query snapshots --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Problem
Changes
How did you test this code?