ruby-next
rubocop-rails
Our great sponsors
| ruby-next | rubocop-rails | |
|---|---|---|
| 6 | 7 | |
| 674 | 740 | |
| 2.4% | 1.4% | |
| 0.0 | 0.0 | |
| about 1 month ago | about 16 hours 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.
ruby-next
-
GitHub - keygen-sh/typed_params: Define structured and strongly-typed parameter schemas for your Rails controllers
But if it really bothers you, check out ruby-next.
-
GitHub - saturnflyer/polyfill-data: Adds the Ruby 3.2 Data class to lower Ruby versions
I hope to get some time to try to contribute it to ruby-next https://github.com/ruby-next/ruby-next/issues/98
-
Future of Ruby – AST Tooling
As it would happen, the folks behind Ruby Next have some ideas here, and have done a significant amount of work in enabling this very vision to become a reality.
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.
-
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
What are some alternatives?
Django - The Web framework for perfectionists with deadlines.
coc-solargraph - Solargraph extension for coc.nvim
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
rubocop-performance - An extension of RuboCop focused on code performance checks.
gringotts - A complete payment library for Elixir and Phoenix Framework
fast - Find in AST - Search and refactor code directly in Abstract Syntax Tree as you do with grep for strings
stripity_stripe - An Elixir Library for Stripe
unparser - Turn Ruby AST into semantically equivalent Ruby source
Vagrant - Vagrant is a tool for building and distributing development environments.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
typed_params - An alternative to Rails strong_parameters. Define structured and strongly-typed parameter schemas for your Rails controllers.