feat: implement LMS chapters list including filtering and sticky header#9
feat: implement LMS chapters list including filtering and sticky header#9Gowreesh-A-M wants to merge 2 commits intomainfrom
Conversation
Gowreesh-A-M
commented
Feb 28, 2026
- Created ChaptersListPage with filtering logic
- Implemented CurriculumHeader with sticky behavior
- Created ChapterCurriculumItem and LessonListItem with premium visual styling
- Integrated courseDetailProvider and allCourseLessonsProvider for curriculum data
- Updated app_router.dart and StudyScreen for seamless navigation
- Added localized strings and generated assets
- Created ChaptersListPage with filtering logic - Implemented CurriculumHeader with sticky behavior - Created ChapterCurriculumItem and LessonListItem with premium visual styling - Integrated courseDetailProvider and allCourseLessonsProvider for curriculum data - Updated app_router.dart and StudyScreen for seamless navigation - Added localized strings and generated assets
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the LMS study experience by introducing a structured curriculum view. Users can now navigate through course chapters and lessons hierarchically, filter content by type, and benefit from a persistent sticky header for improved navigation. This change provides a more organized and user-friendly way to interact with complex course materials. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a new chapters list page with filtering, which is a great addition. My review focuses on improving the provider implementation for better performance and error handling, increasing the robustness of the filtering logic, completing the navigation flow, and addressing some minor maintainability and internationalization issues. The most significant suggestion involves refactoring the courseDetailProvider to be asynchronous, which will require updates to its consumers but will result in a more correct and performant data layer.
| final l10n = L10n.of(context); | ||
|
|
||
| // Consistent blue for course/chapter icons as per reference | ||
| final iconTheme = design.study.pdf; // Blue theme (EFF6FF / 2563EB) |
There was a problem hiding this comment.
The iconTheme is hardcoded to use design.study.pdf. While the comment explains this is to get a consistent blue color, it creates a "magic link" between chapters and the PDF lesson type theme. This can be confusing for future developers and less maintainable if the PDF theme changes.
For better clarity and maintainability, consider defining a specific theme for chapters within DesignStudyTheme (e.g., design.study.chapter) or using a more generic theme if available.