Repository navigation
feat(account): decouple account management and storage from legacy Preferences - #11708
Merged
wmontwe merged 20 commits intoOct 15, 2026
Conversation
Contributor
|
✅ Validation Passed: All report and feature-flag labels are correctly set. |
Member
Author
|
I opened this as draft as there is still a known bug with the special folder mapping during account creation. This is an old bug, that surfaces now consistently. |
wmontwe
marked this pull request as ready for review
October 12, 2026 17:06
wmontwe
force-pushed
the
feat-decouple-account-usage-from-legacy-account-part-2
branch
from
October 12, 2026 17:16
dda882c to
848dcd5
Compare
wmontwe
force-pushed
the
feat-decouple-account-usage-from-legacy-account-part-2
branch
from
October 12, 2026 17:31
848dcd5 to
377a45c
Compare
rafaeltonholo
left a comment
Member
There was a problem hiding this comment.
Since GitHub plugin feels a bit buggy, I will already comment the findings I've got so far.
Reviewed 301/494 files so far.
rafaeltonholo
left a comment
Member
There was a problem hiding this comment.
Since GitHub plugin feels a bit buggy, I will already comment the findings I've got so far.
Reviewed 301/494 files so far.
wmontwe
force-pushed
the
feat-decouple-account-usage-from-legacy-account-part-2
branch
from
October 14, 2026 13:49
6ec0f85 to
8a55849
Compare
wmontwe
force-pushed
the
feat-decouple-account-usage-from-legacy-account-part-2
branch
from
October 14, 2026 16:03
8a55849 to
7a39a4d
Compare
…cation ID registry
wmontwe
force-pushed
the
feat-decouple-account-usage-from-legacy-account-part-2
branch
from
October 15, 2026 15:19
67098be to
360ae2e
Compare
1 of 3 tasks
wmontwe
deleted the
feat-decouple-account-usage-from-legacy-account-part-2
branch
October 15, 2026 16:15
This branch was successfully deployed
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.
Contribution Summary
Linked Issue/Ticket: Resolves #11644
RFC / Technical Design (if applicable):
Description
Decouple account management and persistence from the legacy K-9 Preferences singleton and remove LegacyAccountDto / LegacyAccountDtoManager.
This removed Legacy God-Objects & DTOs:
Preferences.ktthe old singleton holding account state in memory.LegacyAccountDto.kt&LegacyAccountDtoManager.kt.DefaultLegacyAccountDataMapper.kt.NotificationIds.ktand replaced with dynamicAccountNotificationIdRegistry.API Migration:
LegacyAccountDtoandPreferences.getPreferences(...)with type-safeAccountIdandLegacyAccountManager.Testing
As this touches the app vertically, testing was done by ensuring all existing tests are either reworked of green. Added a couple of tests to verify behavior that was previously untested.
AI Disclosure
Select one of the following (mandatory)
Stack