Rails/HttpStatus doesn't detect status key properly

[btoconnor]

I recently upgraded to 0.54.0 and noticed that the new Rails/HttpStatus cop was not picking up the following issue:

render status: 201, json: {}

After spending an hour or so ensuring that everything was setup properly, I went and tried the following:

render json: {}, status: 201

and that code correctly tripped the new HttpStatus error.

---

Expected behavior

I expected rubocop to pick up the status parameter to render regardless of position

Actual behavior

Rubocop did not trigger a linting error. It correctly triggers a linting issue when the code is formatted as

render json: {}, status: 201

Screenshot from my editor with rubocop integrated:

Steps to reproduce the problem

In a controller, write

render status: 201, json: {}

with Rails/HttpStatus enabled, and EnforcedStyle set to symbolic (the default)

RuboCop version

Include the output of rubocop -V. Here's an example:

$ rubocop -V
0.54.0 (using Parser 2.5.0.5, running on ruby 2.4.2 x86_64-linux)

[a14m]

I'm still experiencing the same issue

      # POST /videos
      def create
        # ...
        render status: 201, json: video
      end

      # DELETE /videos/1
      def destroy
        # ...
        head :no_content
      end

it doesn't detect any violation (no matter whether the EnforcedStyle is set to numeric or symbolic)

$ rubocop -V
0.55.0 (using Parser 2.5.1.0, running on ruby 2.5.1 x86_64-darwin17)

Apparently it has something to do with rubocop-rspec plugin
after removing require: rubocop-rspec from .rubocop.yml it started working properly again