🐛 Fix date range for statistics requests #478
Merged
Conversation
This file contains 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
The date range for statistics requests was not correctly handled, leading to inaccurate results. This commit fixes the issue by: - Changing the date range parameters in the StatisticsService to use ZonedDateTime instead of LocalDate. - Updating the StatisticsViewModel to correctly format the date range for the API request. - Updating the Statistics composable to use UTC for the date range picker.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The date range for statistics requests was not correctly handled, leading to inaccurate results. This commit fixes the issue by:
fixes #266
fixes #268