Repository navigation
Fix/account settings - #32
Closed
albert-gee wants to merge 8 commits into
Closed
albert-gee wants to merge 8 commits into
albert-gee wants to merge 8 commits into
Conversation
* Make supported database migrations atomic through schema version commit * Keep optimistic task mutations intact during remote imports * Preserve native recurrence durations and completed task history * Correct schedule dates, pending list visibility and ongoing events * Exclude private Android support files from backup and transfer * Preserve yearly month-day expansion in recurrence editing * Preserve calendar deletion identities, reminder revisions and zoned durations * Preserve active DAV task state through completion and queued edits * Force fresh native Microsoft acquisition for unauthorized retries * Keep Microsoft refresh recovery scoped to each native token request * Reanchor ordinary series edits while preserving exception schedules Use one validated recurrence plan for the ordinary editor, optimistic projection, queued request, and provider payload. Confirm changes that alter the recurrence pattern, preserve its ending mode, and leave guarded drag operations on their established timing path. Associate modified and cancelled exceptions with provider-resolved recurrence positions while retaining their authored schedules. Persist replay phases and checked provider state so response loss, local identity replacement, and restart cannot apply the timing change twice or discard exception recovery data. Preserve dependent edits and stop before provider writes when exception preservation cannot be established. Keep the earlier Google series on its local weekday when splitting across a UTC date boundary. Add normal-editor, HTTP-client, DAV-resource, persistence, recovery, and pattern regressions covering weekly, monthly, ordinal, multiple-weekday, ending, all-day, and DST cases. Validation: 3,773 Flutter tests passed (10 credential-gated live-provider skips), clean analysis/format/platform checks, Linux release and Android debug builds. Native Android, Python, and portable C++ checks also passed for the integrated correction set. * Keep recurring event timing consistent through replay and rescheduling Preserve the validated UNTIL boundary when splitting a Google series. Resolve exception schedules consistently in projection and restoration, retaining checked provider revisions through interrupted replay. Reanchor pointer rescheduling while preserving its exception policy and requiring confirmation for semantic pattern changes. Validated with 3791 passing Flutter tests and 10 live-provider skips, 153 focused replay regressions, clean analysis and formatting, platform boundaries, a Linux release build, and an Android debug build.
Coordinate DAV credential commits and removals with linked contacts, cancel abandoned Login Flow attempts, and revalidate blocked Nextcloud accounts. Preserve multiple accounts and issuer-bound reconnects, recover contacts with real authorization, and present actionable Yaru account and calendar states. Add regression coverage for removal and cancellation races, account isolation, registration recovery, visibility, sync outcomes and native Linux acceptance.
Release authorization serialization before restoring contacts after failed Nextcloud removal, while retaining account coordination and generation checks. Use the current verified parent credential for every linked CardDAV request. Offer native per-calendar Retry and Discard actions for failed Google visibility writes through the existing pending-operation recovery service. Cover production credential-reader locking, queued replacement, ordinary parent reconnect, account isolation and 403 recovery. Drive scheduled-contact coverage with a controlled timer instead of a timing-dependent sleep.
Name the calendar and list every setting restored when discarding its queued personal-settings patch. Explain that local selection is retained and no changes are sent to Google, using a calendar-specific localized confirmation. Exercise visibility-only and merged color/visibility patches through Settings, the repository and pending-operation service, including Cancel, restoration, local controls and account isolation. Capture native confirmations in light and dark themes at normal and narrow window sizes.
Open calendar/task and independent contact accounts by stable ID within Settings. Restore overview scroll and focus, cancel owned authorization on navigation, and keep unrelated synchronization running. Use standard Yaru preference groups, compact collection controls, explicit Google visibility settings, and advanced registration disclosures. Present safe recovery messages without hiding distinct Calendar and Tasks outcomes. Preserve the account lifecycle and scoped calendar Retry/Discard fixes. Add behavioral navigation, cancellation, collection, status, and Linux acceptance coverage, and adapt auth-routing regressions to the account detail views.
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.