Day 36. What is the power of Pull Request?

#android #100daysofcode #kotlin #mobile

What is the power of Pull Request? Is it useful when you work alone? I think It is a great tool for collaboration and personal growth when you review code or when your code is reviewed. I miss having true code review.

What I did:

What did I do today? I spent half of my time trying to fix minor issues that CodeRabbit generated. It looks slightly boring: looking at the issue, finding it in the code, making changes, and committing. If the task is bigger than just removing something, you should spend time thinking about how to refactor. At this moment, it feels like a waste of time. So I will focus only on critical issues that I find reasonable. I think CodeRabbit is a good tool if you are a solo developer with plenty of time.

Additionally, I started working on the UI for the SearchScreen. I added my version of a Chip for sorting and selecting a search type. I reused my SortingChip component. Since I had used it on another screen, I refactored its implementation to make it more type-independent. I introduced a generic type for this composable.

This allowed me to use it with three different type of sorting chips. I added these chip buttons to the SearchScreen. Now it looks a bit rough, but I believe that soon, a designer will join the project and help me with this pain.