Create v2 of stats trends with segmentation #975
Draft
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.
Create v2 of stats trends with segmentation and requesting specific fields
🗣 Description
Adds segentation capability when a user requests a date range over 60 days. Also adds the ability to request specific fields to avoid getting irrelevant data.
💭 Motivation and context
There are future plans for long term trending being shown on the front end. To serve the relevant data we need to be able to streamline the return to be only the relevant data. This means the user should be able to specify specific fields and request data to be aggregated based on a date segments.
🧪 Testing
Tested locally and tests have been written in pytest to test different capabilities.
✅ Pre-approval checklist