Ideally your PR should not include too many changes. Split a huge PR to several small once so that it's easier to quickly find any regressions might be introduced by your code.
-
✅ To the best of my ability, I have made sure that the code I have written is as simple and as straight forward as possible.
-
✅ I have kept the following in mind as I was writing my code
- ✅ Single Responsibility Principle to avoid god components and methods
- ✅ Loose Coupling, Sependency Injection, Complex logic simplification
-
✅ Component Composition model for crafting reusable code