End of year code clean-up
See original GitHub issueAfter running the JetBrains code inspection tool it pointed out a bunch of code issues which are not errors but could be cleaned up. Stuff like unnecessary type parameters, unused variables, redundant using
directives, etc…
It would be nice to clean these things up as end of year activity and start the year off with fresh clean code. Any PR that I make to clean things up would go against this issue.
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Code Cleanup: 7 Simple Daily Steps That Pay off in the End
Code cleanup doesn't have to be an arduous job. Learn seven simple steps you can perform daily to keep your codebase in great...
Read more >Is it a good idea to schedule regular time to clean up code?
No. Fix it while you're working on it : If you wait to refactor the bit you're working on, you'll forget a lot...
Read more >Spring Cleaning: Clean Up Your Code
It erases the mistakes from your original code so it's easy to compare the original to the cleaned up version to see where...
Read more >5 Tips For Cleaner Code // Clean Up Your Code ... - YouTube
5 Tips For Cleaner Code // Clean Up Your Code With These 5 Tips in 2020 For Developers. 7.4K views · 2 years...
Read more >10 Tips For Writing Cleaner Code In Any Programming ...
10 tips for writing cleaner code in any programming language · 1. Use descriptive names · 2. Use empty lines to create 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
OK, I have experience with this type of work - will break it down in stages and invite you to review PRs @bolatovumar.
However we do need @NicolasDorier and @Kukks to finish their PRs first. Because if I start going wild with my tooling - merging pending PRs will be extreme pain with all the changes across complete codebase.
Probably won’t have time to work on this so closing for now.