Conversation
- Add new menu xml entry for people - Add search menu to Toolbar - Migrate people adapter from ArrayAdapter to BaseAdapter - Implement search and filter - Handle empty state
|
Thanks! However, these changes have such fundamental issues that I wonder if this was created using an LLM coding agent? If you wrote this yourself, I suggest having a look at for example https://developer.android.com/topic/architecture#common-principles |
|
Hi, I would like to express my graditute as I use your application since more than a decade! 🙏 When implementing this PR I had a nostalgic blast from the past as the architecture used in this part of the applications is ancient. It uses a List, not even a RecyclerView – something I havn't seen since ~2012? 😄 |
Thank you!
My main concern is about architecture, not APIs. As you seem interested in working on this, I'll go into details. It's a learning exercise for me. But it's OK if you drop this, I can get to this myself at some point. The main issue is that the adapter class is used to modify the data when it's purpose is just to bind data to the UI. There is an existing view model class that's responsible for obtaining and keeping the current state of the credits data. UI events, like the search, should trigger logic in the view model. Which then should update the credits data. But there are many other small things to improve like
|
- Reset PeopleAdapter - Move search to ViewModel - Introduce MenuProvider - Add new hint Strings for search
|
Thanks for your patience, I managed to:
|
Adds a search icon to the crew and cast list to filter for name and role.
.contains()for name and description