feat: Calendar sync status - #110
Draft
benjaminVadon wants to merge 2 commits into
Draft
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds per-calendar synchronization statuses, persisting outcomes while overlaying active synchronization at runtime.
Changes:
- Introduces sync status and error domain models.
- Persists synchronization timestamps and failures in Room.
- Updates repository behavior and adds status-focused tests.
Reviewed changes
Copilot reviewed 19 out of 19 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
EventRepositoryTest.kt |
Updates calendar test fixtures. |
CalendarRepositoryTest.kt |
Tests sync outcomes and runtime status. |
CalendarEntityToDomainSyncStatusTest.kt |
Tests persisted-status mapping. |
EventDaoTest.kt |
Updates calendar fixtures. |
CalendarDaoTest.kt |
Tests sync bookkeeping queries. |
AccountDaoTest.kt |
Updates calendar fixtures. |
SyncErrorReason.kt |
Defines coarse failure reasons. |
CalendarSyncStatus.kt |
Defines public synchronization states. |
Calendar.kt |
Exposes calendar sync status. |
SyncStateHolder.kt |
Tracks active calendar syncs. |
CalendarRepository.kt |
Records and exposes sync lifecycle state. |
ThrowableToSyncErrorReason.kt |
Maps failures to domain reasons. |
RemoteDavCalendarToEntity.kt |
Preserves local sync state during refresh. |
CalendarEntityToDomain.kt |
Maps bookkeeping to domain status. |
CalendarSyncStateEntity.kt |
Groups persisted sync fields. |
CalendarEntity.kt |
Embeds synchronization bookkeeping. |
DatabaseProvider.kt |
Advances the database schema version. |
CalendarDao.kt |
Adds success and failure updates. |
13.json |
Exports the Room v13 schema. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
benjaminVadon
force-pushed
the
calendar-sync-status
branch
2 times, most recently
from
July 30, 2026 14:26
f4503b5 to
f3bb913
Compare
benjaminVadon
force-pushed
the
calendar-sync-status
branch
2 times, most recently
from
August 18, 2026 16:05
c3a9864 to
bc6aafb
Compare
benjaminVadon
force-pushed
the
calendar-sync-status
branch
2 times, most recently
from
September 8, 2026 13:10
24b160e to
cdd2f68
Compare
benjaminVadon
marked this pull request as draft
September 9, 2026 12:43
benjaminVadon
force-pushed
the
calendar-sync-status
branch
2 times, most recently
from
September 11, 2026 09:08
90cf546 to
8a5d9c9
Compare
benjaminVadon
force-pushed
the
calendar-sync-status
branch
from
September 11, 2026 14:16
8a5d9c9 to
a4966e2
Compare
|
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
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.
No description provided.