Add channel/rubocop-1-12-1 (#281)

* Update rubocop to v1.12.1

* Update scraped documentation

Author: timlkelly

Gemfile

@@ -6,7 +6,7 @@ gem "activesupport", require: false
 gem "mry", require: false
 gem "parser"
 gem "pry", require: false
-gem "rubocop", "1.12.0", require: false
+gem "rubocop", "1.12.1", require: false
 gem "rubocop-i18n", require: false
 gem "rubocop-graphql", require: false
 gem "rubocop-minitest", require: false

Gemfile.lock

@@ -41,7 +41,7 @@ GEM
       diff-lcs (>= 1.2.0, < 2.0)
       rspec-support (~> 3.9.0)
     rspec-support (3.9.3)
-    rubocop (1.12.0)
+    rubocop (1.12.1)
       parallel (~> 1.10)
       parser (>= 3.0.0.0)
       rainbow (>= 2.2.2, < 4.0)
@@ -93,7 +93,7 @@ DEPENDENCIES
   pry
   rake
   rspec
-  rubocop (= 1.12.0)
+  rubocop (= 1.12.1)
   rubocop-graphql
   rubocop-i18n
   rubocop-minitest

config/contents/style/access_modifier_declarations.md

@@ -42,7 +42,7 @@ using AllowModifiersOnSymbols config.
 
     end
 
-### Example: AllowModifiersOnSymbols: true
+### Example: AllowModifiersOnSymbols: true (default)
     # good
     class Foo
 

config/contents/style/frozen_string_literal_comment.md

@@ -5,9 +5,6 @@ files to enable frozen string literals. Frozen string literals may be
 default in future Ruby. The comment will be added below a shebang and
 encoding comment.
 
-Note that the cop will ignore files where the comment exists but is set
-to `false` instead of `true`.
-
 ### Example: EnforcedStyle: always (default)
     # The `always` style will always add the frozen string literal comment
     # to a file, regardless of the Ruby version or if `freeze` or `<<` are

config/contents/style/method_call_with_args_parentheses.md

@@ -35,8 +35,12 @@ options.
       to `true` allows the presence of parentheses in such a method call
       even with arguments.
 
-NOTE: Parens are required around a method with arguments when inside an
-endless method definition (>= Ruby 3.0).
+NOTE: Parentheses are still allowed in cases where omitting them
+results in ambiguous or syntactically incorrect code. For example,
+parentheses are required around a method with arguments when inside an
+endless method definition introduced in Ruby 3.0.  Parentheses are also
+allowed when forwarding arguments with the triple-dot syntax introduced
+in Ruby 2.7 as omitting them starts an endless range.
 
 ### Example: EnforcedStyle: require_parentheses (default)