ezcater_rubocop 5.1.0 → 5.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3dbb408ffa690e48915809b4f55644601682034469f8b59d0f73624b2a1a225f
-  data.tar.gz: 75aa569d52eb164cc9ded5d5c1c776bb658dca665fb6c5c013ca9b0607d71db2
+  metadata.gz: 30c8d52abd3c39c8b776dbaff56aa94f2f010cf6866579b21a00084f22a42c1f
+  data.tar.gz: dc12424a0dd777560c4657ae87539264ec40f6553b3b6aa6aa963051fbc919d2
 SHA512:
-  metadata.gz: 374a5e16b853aabf25af23c4860c6a00f1b457682499fda3f84937d764d5398ab8ae3c34cbcb4c948da51fc7795fe6a7ab14d3686bfe03f8613ffc3663bebc5c
-  data.tar.gz: 880dd4bea07e44db41452388715c763f5a608d3875ff767a3a2c689f69321a076004e71e211e6b60de5b90806a6886a8342336e422f35063ade3c4c76d40854e
+  metadata.gz: 54bb2d3b45ff6bd48f4ab289bb885e3e1c2635cb4b4bfc44d74086d3b46a39db1bb8c1f3c83f53901931f4a9a015ebe3beb780019f078dd5713a64ba41e11aa7
+  data.tar.gz: cbeb087b43166a7f874603862ad0f909e930ee051c89a3f4862dbe18c0a62e2b6bf58d9657155d8dfd5b569bf1d56b6b83804181394fa8e88d0da19ba9d2f68b

data/CHANGELOG.md

@@ -6,6 +6,31 @@ This gem is moving onto its own [Semantic Versioning](https://semver.org/) schem
 
 Prior to v1.0.0 this gem was versioned based on the `MAJOR`.`MINOR` version of RuboCop. The first release of the ezcater_rubocop gem was `v0.49.0`.
 
+## 5.2.1
+- Fix the has the wrong namespace for `RSpec/Capybara/CurrentPathExpectation` and `RSpec/Capybara/VisibilityMatcher` cops, since [they've been extracted](https://github.com/rubocop/rubocop-rspec/blob/master/CHANGELOG.md#2180-2023-01-16) into a separate repo [rubocop-capybara](https://github.com/rubocop/rubocop-capybara).
+
+## 5.2.0
+
+- Add an explicit rule for `Style/HashSyntax`, setting `EnforcedShorthandSyntax: either`.
+
+Ruby 3.1 introduces syntax where named arguments can be passed
+
+```ruby
+name = "Michael"
+method_with_named_args(name:)
+```
+
+rather than
+
+```ruby
+name = "Michael"
+method_with_named_args(name: name)
+```
+
+when the variable's name matches the named argument key.
+
+For now, we have decided to allow either syntax while we upgrade our applications to Ruby 3.1. This is auto-correctable if and when we decide to enforce the new syntax.
+
 ## 5.1.0
 - Change paths to exclude for various cops to be agnostic of directory structure prior to the matching string. This is to allow apps to have greater flexibility in where files live, but still have them excluded from certain cops. The need for this arose when implementing Stimpack, which moves specs and other files under app/packs/[pack_name].
 

data/conf/rubocop.yml

@@ -233,13 +233,13 @@ Rails/Pick:
 Rails/RedundantForeignKey:
   Enabled: true
 
-RSpec/Capybara/CurrentPathExpectation:
+Capybara/CurrentPathExpectation:
   Enabled: true
 
-RSpec/Capybara/FeatureMethods:
+Capybara/VisibilityMatcher:
   Enabled: true
 
-RSpec/Capybara/VisibilityMatcher:
+RSpec/Capybara/FeatureMethods:
   Enabled: true
 
 RSpec/EmptyHook:
@@ -340,3 +340,6 @@ Style/HashTransformKeys:
 
 Style/HashTransformValues:
   Enabled: true
+
+Style/HashSyntax:
+  EnforcedShorthandSyntax: either

data/lib/ezcater_rubocop/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module EzcaterRubocop
-  VERSION = "5.1.0"
+  VERSION = "5.2.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ezcater_rubocop
 version: !ruby/object:Gem::Version
-  version: 5.1.0
+  version: 5.2.1
 platform: ruby
 authors:
 - ezCater, Inc
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-11-17 00:00:00.000000000 Z
+date: 2023-02-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler