mirror of
https://github.com/openfoodfoundation/openfoodnetwork
synced 2026-01-28 21:07:16 +00:00
7ad40074a5
Our rubocop config hides all current violations. It allows us to have a passing rubocop run on the current code and improve it gradually. It detects new violations, but doesn't annoy us with all the existing ones. Code Climate has its own way of remembering all current violations which is more sophisticated than ours. The new config for Code Climate doesn't hide any violations so that Code Climate can give us a realistic score of code quality and warn us about every new violation. Splitting the configuration into the main three parts gives a quicker overview and makes maintaining the parts easier.
21 lines
683 B
YAML
21 lines
683 B
YAML
# This is our main Rubocop configuration for developers. It is used when you run:
|
|
#
|
|
# bundle exec rubocop
|
|
#
|
|
# The configuration is split into three files. Look into those files for more details.
|
|
#
|
|
inherit_from:
|
|
|
|
# The automatically generated todo list to ignore all current violations.
|
|
- .rubocop_todo.yml
|
|
|
|
# Our Open Food Network style guide. It's used by Code Climate. If you want to see all violations,
|
|
# then use only that configuration (like Code Climate):
|
|
#
|
|
# bundle exec rubocop -c .rubocop_styleguide.yml
|
|
#
|
|
- .rubocop_styleguide.yml
|
|
|
|
# A manually compiled todo list to ignore metrics violations on a file-by-file basis.
|
|
- .rubocop_manual_todo.yml
|