Conversation
- Made the 'New' badge in `LibraryDrawerContent.kt` clickable, navigating the user to the latest chapter of the novel. - Renamed `items` to `chapterItems` in `LibraryDrawerContent.kt` to clarify scope. - Updated `LibraryRepository.markAsCurrentlyReading` to clear the `hasUpdates` flag for all items in the novel group (using `baseTitle` or ID). - Added `clearUpdatesForBaseTitle` and `clearUpdatesForId` methods to `LibraryDao`. - Added unit tests in `LibraryRepositoryTest` to verify that reading a chapter clears the update notification.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This change enhances the UX by allowing users to click the "NEW" badge to jump directly to the latest chapter. It also ensures that the badge disappears once the user engages with the novel (by starting to read any chapter), which is handled by clearing the
hasUpdatesflag for the entire novel group in the database. Unit tests were added to verify the update-clearing logic.PR created automatically by Jules for task 17900424728734058605 started by @Aatricks