feat(session): add database preparation boundary PR 1 - #5158
Open
MohamadJaara wants to merge 2 commits into
Open
feat(session): add database preparation boundary PR 1#5158MohamadJaara wants to merge 2 commits into
MohamadJaara wants to merge 2 commits into
Conversation
This was referenced Aug 11, 2026
MohamadJaara
marked this pull request as ready for review
August 11, 2026 16:27
saleniuk
approved these changes
Aug 12, 2026
MohamadJaara
changed the base branch from
mo/epic/async-db-migration
to
develop
August 18, 2026 12:27
MohamadJaara
force-pushed
the
mo/async-db-migration/01-foundation
branch
2 times, most recently
from
August 18, 2026 12:45
c6f2da8 to
0f4d4ce
Compare
Contributor
MohamadJaara
force-pushed
the
mo/async-db-migration/01-foundation
branch
from
August 19, 2026 11:49
0f4d4ce to
4b3b751
Compare
MohamadJaara
force-pushed
the
mo/async-db-migration/01-foundation
branch
from
August 21, 2026 09:55
4b3b751 to
9c397c4
Compare
Contributor
|
@MohamadJaara looks like you are rolling back kalium to a previous commitish. This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.
Is this intentional? |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5158 +/- ##
===========================================
+ Coverage 52.21% 52.24% +0.02%
===========================================
Files 668 669 +1
Lines 23987 24001 +14
Branches 3952 3955 +3
===========================================
+ Hits 12526 12539 +13
- Misses 10301 10302 +1
Partials 1160 1160
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Contributor
|
APKs built during tests are available here. Scroll down to Artifacts! |
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.
Goal
Add the Android boundary for Kalium's explicit user-session database preparation lifecycle.
Changes
Impact
This is a foundation-only change. It introduces no screen or consumer behavior yet; later PRs use this boundary before accessing a user database.
Stack
mo/epic/async-db-migration