You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying rubyfmt on a few different projects, I always end up facing the same problem: I am currently using RuboCop, and after migrating I need to keep using e.g. RuboCop-RSpec, RuboCop-Performance, custom cops etc. While rubyfmt is great for maintaining a consistent layout of my source code (and doing it fast!), RuboCop still has its place for fulfilling my other static analysis needs.
So I thought perhaps it might be useful to maintain a list of cops that people should disable when migrating to rubyfmt. It could either be as a markdown document or as a YAML-formatted RuboCop config file in a separate repo.
There will of course be some maintenance overhead as new versions of RuboCop are released. I have some loose ideas about how to automate it, but I wanted to get feedback from rubyfmt maintainers first.
The text was updated successfully, but these errors were encountered:
While trying rubyfmt on a few different projects, I always end up facing the same problem: I am currently using RuboCop, and after migrating I need to keep using e.g. RuboCop-RSpec, RuboCop-Performance, custom cops etc. While rubyfmt is great for maintaining a consistent layout of my source code (and doing it fast!), RuboCop still has its place for fulfilling my other static analysis needs.
So I thought perhaps it might be useful to maintain a list of cops that people should disable when migrating to rubyfmt. It could either be as a markdown document or as a YAML-formatted RuboCop config file in a separate repo.
There will of course be some maintenance overhead as new versions of RuboCop are released. I have some loose ideas about how to automate it, but I wanted to get feedback from rubyfmt maintainers first.
The text was updated successfully, but these errors were encountered: