Reek
Rubycritic
Our great sponsors
| Reek | Rubycritic | |
|---|---|---|
| 6 | 4 | |
| 3,976 | 3,289 | |
| - | 0.7% | |
| 8.0 | 6.3 | |
| 10 days ago | 3 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Reek
-
First commits in a Ruby on Rails app
Rubycritic uses reek under the hood so I added a reek config files at .reek.yml with the following content:
-
Code Reviewing a Ruby on Rails application.
Reek is a code smell detection tool for Ruby that helps identify potential design issues. It analyzes your codebase and provides feedback on areas that might benefit from refactoring or improvement. Here's an overview of what Reek is and how to use it:
-
Improve Code in Your Ruby Application with RubyCritic
$ reek app/controllers/erp/orders_controller.rb Inspecting 1 file(s): S app/controllers/erp/orders_controller.rb -- 1 warning: [91]:UncommunicativeVariableName: Erp::OrdersController#create has the variable name 'e' [https://github.com/troessner/reek/blob/v6.1.1/docs/Uncommunicative-Variable-Name.md]
-
Gems that can identify churn, complexity, duplication and smells.
reek
-
Security Risks On Rails: Misconfiguration and Unsafe Integrations
Other useful gems you may take a look at are dawnscanner, reek, and hakiri_toolbelt.
-
The best way to review my code for code smells?
Beside RuboCop, I found reek very useful. https://github.com/troessner/reek
Rubycritic
-
First commits in a Ruby on Rails app
The third commit adds Rubycritic as a code quality static analysis.
-
Improve Code in Your Ruby Application with RubyCritic
You should consider using RubyCritic if you want a single place to review code improvements for your project. Including RubyCritic in your development process will certainly reduce the time a development team spends working on technical debts. Most technical debts will be mapped out at development time.
-
Best services and/or gems for automated generation of documentation, unit tests, and useful things of this nature
It's also possible to write unit tests in order to better understand or surface your assumptions about a legacy application. I'd also consider running rubycritic against legacy code, to see where the code smells and other hot spots lie.
-
How to Improve Code Quality on a Ruby on Rails Application
RubyCritic: a gem that wraps around static analysis gems such as Reek, Flay, and Flog to provide a quality report of your Ruby code.
What are some alternatives?
Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
rails_best_practices - a code metric tool for rails projects
Brakeman - A static analysis security vulnerability scanner for Ruby on Rails applications
Flay - Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored.
SimpleCov - Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites
Flog - Flog reports the most tortured code in an easy to read pain report. The higher the score, the more pain the code is in.
Pronto - Quick automated code review of your changes
MetricFu - A fist full of code metrics
Coverband - Ruby production code coverage collection and reporting (line of code usage)
rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide.