You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve error handling in async functions by adding toast notifications for API failures.
Revert messageStatuses to previous state on error in resend and refresh functions.
After resending, fetch and update the message status immediately.
Review and align the week start day (Sunday vs. Monday) in weekly count calculations and daily display.
Consider updating the "lost" status label for null messageUuid to something clearer like "missing" or add a tooltip explaining the status.
Summary of Changes
Updated spec file to mark DailyCountsHistoryView items as completed.
Incremented appVersion to '2025.10.17.5' in utils.ts.
Implemented new DailyCountsHistoryView.vue with picker filter, weekly/daily count displays, and history list with status actions.
Overall Feedback
There's still room for better error handling to prevent silent failures and improve user feedback. ⤑ Also, the date logic for weekly displays needs verification for edge cases. 👍 However, the feature is well-structured and adds nice functionality to the app!
In async functions like loadCompletedDailyCounts, loadMessageStatuses, refresh, and resend, errors are only logged to console. Consider adding user-facing error notifications (e.g., toast messages) to improve UX, as failures might go unnoticed.
In resend and refresh functions, if an error occurs, the messageStatuses is set to "pending" or "refreshing" but not reverted back on failure. Consider reverting to the previous status or handling it appropriately.
After resending a message in resend, consider fetching the updated status from the server to reflect any immediate changes, similar to the refresh function.
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
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.
Related to #63