Include 👃 for Code Smell fixes
See original GitHub issueHello @carloscuesta 😎!
- Emoji: 👃
- Code:
:nose:
- Description:
Describe the use case of your emoji
We use SonarCloud to help us improve our code quality, one of the fixes we have to do regularly is resolving code smells.
Is this use case covered by an existing emoji?
I’ve not seen anything suitable.
Does this emoji fall into the “how” category?
I don’t believe it does.
Examples
👃 SC/CS - Fix unused function parameters should be removed
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Code Smells: What Are They And How Can I Prevent Them?
What is a code smell? In this post we will find that out and also discuss prevent them from occurring in the first...
Read more >7 Steps to Reduce Code Smell 🦨 - DevInterrupted
Does your old code have a plethora of issues? Here are seven tips to lessen your code smell and improve your code.
Read more >Code Smells - Refactoring.Guru
These smells mean that if you need to change something in one place in your code, you have to make many changes in...
Read more >Common Code Smells in Data Science Projects and How to ...
In this article, I've listed some of the most common code smells I encounter when I'm refactoring DS/ML applications. I hope that this...
Read more >Code Smells - Coding Horror
Beware of classes that unnecessarily expose their internals. Aggressively refactor classes to minimize their public surface. You should have a ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Interesting suggestion, however isn’t the ♻️/
:recycle:
an appropriate alternative for a commit focusing on cleaning up code? AFAIK, code smell is kind of a trigger for developers to do refactoring, so also a refactoring is reason of the commit.Hey!
I agree with @piotrkubisa most of the times a code smell triggers a refactor which should be the original purpose of the commit as you’re suppose to change the code without changing the outcome of it!
I think we can safely cover this with ♻️
Thanks for the suggestion!