rubocop-rails
standard
Our great sponsors
rubocop-rails | standard | |
---|---|---|
7 | 18 | |
781 | 2,589 | |
2.2% | 1.9% | |
9.1 | 8.4 | |
5 days ago | 7 days ago | |
Ruby | Ruby | |
MIT License | GNU General Public License v3.0 or later |
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.
rubocop-rails
-
RuboCoping with legacy: Bring your Ruby code up to Standard
1) Auto-correcting a whole (large) codebase at once with tons of offenses and dozens of active branches should be used with caution. Merge conflicts, blame pollution (ok, can be solved with .git-blame-ignore-revs, though can hardly remember any project using it). Though, the most important argument is that auto-correct can introduce bugs. Unfortunately, even safe autocorrect can be unsafe. Recently, I broke one popular project (with a decent, but not 99.999% test coverage) with a single "safe" auto-correction commit 🙂 (This issue).
-
Linting and Auto-formatting Ruby Code With RuboCop
It's also possible to extend RuboCop through additional linters and formatters. You can build your own extensions or take advantage of existing ones if they are relevant to your project. For example, a Rails extension is available for the purpose of enforcing Rails best practices and coding conventions.
-
Technical leadership during large refactors
I'm still getting used to writing these. Still, this article from Evil Martians has been a big help. The rubocop-rails codebase also had some cops similar to what I wanted to put together. The cop we've put together checks if the class inherits from ActiveModel::Serializer and adds an offence to that line.
-
Future of Ruby – AST Tooling
Let's take a glance at the action_filter cop real quick here, but just a quick part of it:
-
Learning style?
Following on from this, I highly recommend setting up your editor to automatically lint Ruby files with RuboCop and its Rails extension and start adapting your code to adhere to the Ruby Style Guide.
- Rails 7 will introduce invert_where method, but it's dangerous
-
Learning Ruby: Things I Like, Things I Miss from Python
I just would like to point out that even though that is the most sane way, it comes with it owns set of problems. One of them is when developers start to code to cheat the linter, or they complicate the code just to "make the linter happy", another is when the linting rule introduces problems/errors like https://github.com/rubocop-hq/rubocop-rails/issues/418
standard
-
Am I the only one who doesn't put parentheses around the parameters in Ruby method definitions?
Rubocop has a default rule that says to put parentheses when there are parameters; even Standardrb has a default ([https://github.com/standardrb/standard/blob/8307fa8f449f896075ccad 74bf6a128ed2c26189/config/base.yml#L1098:title])
- Standardrb: Ruby's bikeshed-proof linter and formatter
-
Must-have gems for mature Rails
gem "rubocop" - https://github.com/rubocop/rubocop | Set up code guidelines for your dev team, I recommend using whatever Standard recommends.
-
A Writer's Ruby
Cynically, reading heavily between the lines, this reads to me like DHH just found out lots of rubyists like standardrb. https://github.com/standardrb/standard -- and this is his quick reaction to it.
-
"Useless Ruby sugar": Endless (one-line) methods
This is a huge reason why I still use StandardJS and—shifting back to Ruby—why I rejected the countless requests for implementing line-length or any other metrics analysis rules for [StandardRB](https://github.com/standardrb/standard). There is always a legitimate edge case when it comes to length of lines and functions and the alternative—chopping them off arbitrarily—is rarely an improvement.
-
An Introduction to RuboCop for Ruby on Rails
This approach is known as Standard Ruby. It can also be completed with plugins, including one for Ruby on Rails projects.
-
It's Official: the Standard Ruby VS Code extension
Oh, this is fantastic! Would you be willing to send a quick PR to our README?
-
Rails vs Rubocop?
[0] https://github.com/testdouble/standard
-
Linting and Auto-formatting Ruby Code With RuboCop
If you don't want to fiddle with configuration files and the wealth of options provided by RuboCop, consider taking a look at the Standard project. It's largely a pre-configured version of RuboCop that aims to enforce a consistent style in your Ruby project without allowing the customization of any of its rules. The lightning talk where it was first announced gives more details about its origin and motivations.
- Utilizando o padrĂŁo interactor no Ruby on Rails
What are some alternatives?
Django - The Web framework for perfectionists with deadlines.
Ruby style guide - A community-driven Ruby coding style guide
coc-solargraph - Solargraph extension for coc.nvim
eslint-config-standard - ESLint Config for JavaScript Standard Style
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
rubocop-rspec - Code style checking for RSpec files
rubocop-performance - An extension of RuboCop focused on code performance checks.
ansi-strikethrough - The color strikethrough, in ansi.
gringotts - A complete payment library for Elixir and Phoenix Framework
Hanami::Model - Ruby persistence framework with entities and repositories
unparser - Turn Ruby AST into semantically equivalent Ruby source
success-symbol - Cross-platform success symbol.