Skip to content

Instantly share code, notes, and snippets.

@ConorSheehan1
Last active December 29, 2021 14:07
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ConorSheehan1/ed75920ca8722a09b527b37f006cf8e3 to your computer and use it in GitHub Desktop.
Save ConorSheehan1/ed75920ca8722a09b527b37f006cf8e3 to your computer and use it in GitHub Desktop.
My personal preference for ruby style
# add indent after access modifier e.g. private
Layout/IndentationConsistency:
EnforcedStyle: indented_internal_methods # previously rails style
# Use double quotes by default, common in large projects including rails
# https://anti-pattern.com/always-use-double-quoted-strings-in-ruby
Style/StringLiterals:
Enabled: true
EnforcedStyle: double_quotes
Style/ColonMethodCall:
Enabled: false
# use %r for long expressions e.g shared_constants acronym_regex
Style/RegexpLiteral:
Enabled: false
# prefer parens for method calls with args
# exceptions for Gmefile, spec, require, etc. type methods
Style/MethodCallWithArgsParentheses:
Enabled: true
IgnoredMethods:
- expect
- gem
- include
- load
- require
- require_relative
- raise
- ruby
- source
- to
- to_not
- not_to
- be
- eq
- have_title
- have_css
- have_xpath
- match
# don't like .zero? instead of == 0
Style/NumericPredicate:
Enabled: false
# preferred method aliases
Style/CollectionMethods:
Enabled: true
PreferredMethods:
collect: map
collect!: map!
inject: reduce
detect: find
find_all: select
# TODO: prefer length / size to count when no args ar present for performance (count O(n), length o(1))
# https://stackoverflow.com/questions/53480273/are-there-performance-reasons-to-prefer-size-over-length-or-count-in-ruby
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment