Repository navigation
feat: user upload heatmap - #28593
Merged
Merged
Conversation
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.
Description
Adds a GitHub-style upload heatmap to Account Settings -> Usage Statistics -> Upload activity.
The backend exposes daily upload counts for the current user through
GET /users/me/stats/uploads. Query parameters are validated through a DTO, date range defaults live in the service, and the repository performs a single UTC grouped SQL query by upload day.The web usage statistics page fetches the last 52 weeks of upload counts and renders a responsive heatmap.
Fixes # (issue)
How Has This Been Tested?
pnpm --dir server checkpnpm --dir web check:svelteScreenshots (if appropriate)
Added
GET /users/me/stats/uploads?from=YYYY-MM-DD&to=YYYY-MM-DDResponse:
{ "userId": "uuid", "from": "2025-05-25", "to": "2026-05-24", "series": [{ "date": "2026-05-24", "count": 3 }], "summary": { "totalCount": 3 } }Checklist:
src/services/uses repositories implementations for database calls, filesystem operations, etc.src/repositories/is pretty basic/simple and does not have any immich specific logic (that belongs insrc/services/)Please describe to which degree, if any, an LLM was used in creating this pull request.
To understand the codebase, LLM was used. The changes were made by me, and to further top it off, LLM was used to write this description.
...