You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Definition 📖
Limit the number of parameters per unit to at most 4.
Why❓
Keeping the number of parameters low makes units easier to understand, test and reuse.
How 🔧
Reduce the number of parameters by grouping related parameters into objects. Alternatively, try extracting parts of units that require fewer parameters.
ℹ️ To know how many other refactoring candidates need addressing to get a guideline compliant, select some by clicking on the 🔲 next to them. The risk profile below the candidates signals (✅) when it's enough! 🏁
Good luck and happy coding! ✨ 💯
The text was updated successfully, but these errors were encountered:
I've selected paymentsHandler(w http.ResponseWriter, r *http.Request, u domainUsers.User) for refactoring, which is a unit of 25 lines of code and 3 parameters. Addressing this will make our codebase more maintainable and improve Better Code Hub's Keep Unit Interfaces Small guideline rating! 👍
Here's the gist of this guideline:
Limit the number of parameters per unit to at most 4.
Keeping the number of parameters low makes units easier to understand, test and reuse.
Reduce the number of parameters by grouping related parameters into objects. Alternatively, try extracting parts of units that require fewer parameters.
You can find more info about this guideline in Building Maintainable Software. 📖
ℹ️ To know how many other refactoring candidates need addressing to get a guideline compliant, select some by clicking on the 🔲 next to them. The risk profile below the candidates signals (✅) when it's enough! 🏁
Good luck and happy coding! ✨ 💯
The text was updated successfully, but these errors were encountered: