I recently found out about Reek from watching Sandi Metz's talk from RailsConf 2016 (great intro to code smells btw).
...
For further actions, you may consider blocking this person and/or reporting abuse
I use it on all my work projects in concert with rubocop. I feel that reek and rubocop are complimentary for the most part; where rubocop cares more about style, and reek cares more about how you code. Where they overlap, I disable one or the other. I also use them during CI for static code analysis through the pre-commit framework, here: pre-commit.com
I think there's a bug, it highlighted my entire
~/Work
folder...Looks nice. How does this compare/contrast with other static analysis tools in Ruby?
Reek is quite opinionated because it focuses on code smells. It's going to flag lots of stuff in a big codebase like dev.to's but it doesn't hurt :-D
There are overlaps with Rubocop IIRC
See the list of code smells. You're probably going to disable Uncommunicative Name for a while because usually it's a high frequency violation.
It might help getting to fewer issues on codeclimate 🤞🏾
I haven't done Ruby in a bit but when I do I'll add this for sure next time I use it in a project.
Fun, it can be viewed as an expert to learn from. Thanks for share.
Would you look at that.
I'm currently working on a similar tool for python
Tadaboody / good_smell
A linting/refactoring library for python best practices and lesser-known tricks
Good Smell - it makes your code smell good!
A linting/refactoring library for python best practices and lesser-known tricks
Installing:
Usage:
good_smell warn - Print warnings about smells in the code
Alternativly you can run it through flake8. Smells will be with the code SMLxxx
good_smell fix - Print a fixed version of the code
Supported code smells:
Range(len(sequence))
will be fixed to
Directly nested for loops
to
Developing
Clone the repository and run inside it
This will install the requirements and…
I'll be looking at this for inspiration. Thanks!