standard
Overcommit
standard | Overcommit | |
---|---|---|
18 | 5 | |
2,606 | 3,876 | |
1.0% | - | |
8.0 | 6.6 | |
4 days ago | 9 days ago | |
Ruby | Ruby | |
GNU General Public License v3.0 or later | 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.
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
Overcommit
-
Linting and Auto-formatting Ruby Code With RuboCop
A great way to ensure that all Ruby code in a project is linted and formatted properly before being checked into source control is by setting up a Git pre-commit hook that runs RuboCop on each staged file. This article will show you how to set it up with Overcommit, a tool for managing and configuring Git pre-commit hooks, but you can also integrate RuboCop with other tools if you already have an existing pre-commit workflow.
-
Tailwind CSS class sorter – the custom way
As a team we want to ensure that everybody commits our templates with classes rightly ordered. We use Overcommit to enforce consistency but any similar tool will do.
-
Run RuboCop on git commit with Overcommit Gem
# Use this file to configure the Overcommit hooks you wish to use. This will # extend the default configuration defined in: # https://github.com/sds/overcommit/blob/master/config/default.yml # # At the topmost level of this YAML file is a key representing type of hook # being run (e.g. pre-commit, commit-msg, etc.). Within each type you can # customize each hook, such as whether to only run it on certain files (via # `include`), whether to only display output if it fails (via `quiet`), etc. # # For a complete list of hooks, see: # https://github.com/sds/overcommit/tree/master/lib/overcommit/hook # # For a complete list of options that you can use to customize hooks, see: # https://github.com/sds/overcommit#configuration # # Uncomment the following lines to make the configuration take effect. PreCommit: RuboCop: enabled: true on_warn: fail # Treat all warnings as failures problem_on_unmodified_line: ignore # run RuboCop only on modified code
-
Automatically sorting your Tailwind CSS class names
Overcommit - run rustywind --write during git commit to update your files before you send them off to git
-
Migrating Tachyons to Tailwind CSS (III – learnings)
By the way, it’s nice that adding (or completely redefining) the scale system is so easy in Tailwind. On the other hand, care must be taken that modifying the defaults is not overused. In the end, we added an Overcommit rule banning further updates of the Tailwind configuration (of course, this can be temporarily disabled, when truly needed).
What are some alternatives?
Ruby style guide - A community-driven Ruby coding style guide
Rugged - ruby bindings to libgit2
eslint-config-standard - ESLint Config for JavaScript Standard Style
git-up - NOT MAINTAINED
rubocop-rspec - Code style checking for RSpec files
git-whence - Find the merge and pull request a commit came from + fuzzy search for cherry-picks
ansi-strikethrough - The color strikethrough, in ansi.
git-spelunk - git-spelunk, an interactive git history tool
rubocop-rails - A RuboCop extension focused on enforcing Rails best practices and coding conventions.
git-auto-bisect - Find the first broken commit without having to learn git bisect
Hanami::Model - Ruby persistence framework with entities and repositories
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.