Use novel refactor#27
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughReplaces the hook-based novel layer with a Zustand-backed persistent store, introduces persistence/key contracts and bootstrap services, updates consumers to selector/action hooks, adds MMKV/Zustand adapters, synchronous DB helpers, and extensive tests and mocks. Also updates package dependencies. Zustand-backed Novel Store & Persistence
Database & Query Changes
Misc / Packaging
Sequence Diagram(s)sequenceDiagram
participant UI as UI Component
participant Selector as Selector Hook
participant Store as Zustand Store
participant Persist as novelPersistence (MMKV)
participant Bootstrap as Bootstrap Service
participant DB as Database
UI->>Selector: read state (chapters/novel/etc.)
Selector->>Store: selector query
Store-->>Selector: state slice
Selector-->>UI: returns state
UI->>Selector: dispatch action (e.g., bootstrapNovel / getNextChapterBatch)
Selector->>Store: invoke action
Store->>Persist: read/write pageIndex/settings/lastRead
Store->>Bootstrap: request chapters/novel data
Bootstrap->>DB: query novel/chapters (sync or async)
DB-->>Bootstrap: data
Bootstrap-->>Store: update chapters/pages/batchInformation
Store-->>UI: state updated
UI->>Selector: request chapter text
Selector->>Store: chapterTextCache.read(id)
alt cache hit
Store-->>UI: return cached text
else cache miss
Store->>DB: (or fetch) obtain chapter text
Store->>Persist: optional persist lastRead/progress
Store-->>UI: text available
end
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
|
2547835 to
06f0f66
Compare
…mocksContract Final validation confirms mock-contract test suite clean and target file deletion verified with zero stale references in src/ scope.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
I want to change the pagination ui, but this is for another pr |
This comment was marked as resolved.
This comment was marked as resolved.
|
..19 since you are dealing with novelscreen |
|
..20 Maybe this feature too. |
|
..21 (dunno if this pr fault) start-reading isnt fixed to the very first chap but the first chap of the single page. YouCut_20260419_062501713.mp4 |
This comment was marked as resolved.
This comment was marked as resolved.
|
..23 Flawed pagination implementation ui (i know you said u will remake the pag ui, this is a suggestion for the remaking) It is counter-intuitive to put the 1st chapter list in the Last page. If tge users sorts descending, the displayed paging should simply invert: Current behaviourAscending: DESCENDING: Expected behaviourDESCENDING: |
This is some issue with legendlist. It doesn't happen with more chapters. Since it isn't an easy fix I don't want to include it here. |
This comment was marked as resolved.
This comment was marked as resolved.
|
Did you build the new version yourself, if not then you didn't update. As this isn't the master branch I need to trigger builds manually and I didn't after I pushed. I did now |
Could you report it on their repo? The dev is very responsive. |
This comment was marked as resolved.
This comment was marked as resolved.
Not yet, as I first need to check if it really is the problem and then I need to check if it is already solved in the beta version. |
Summary by CodeRabbit
New Features
Bug Fixes
Documentation
Chores
Tests