Skip to content

Conversation

@giverm
Copy link
Contributor

@giverm giverm commented Nov 14, 2025

Adds the rubocop-rspec_rails gem to provide Rails-specific RSpec linting.

Enables the RSpecRails/HttpStatusNameConsistency cop to enforce using :unprocessable_content instead of the deprecated :unprocessable_entity for HTTP 422 status codes.

Sets NewCops to disabled to prevent automatic enablement of new cops in future gem updates, allowing us to evaluate and enable them deliberately.

@giverm giverm requested a review from doshitan November 14, 2025 20:20
Adds the rubocop-rspec_rails gem to provide Rails-specific RSpec linting.

Enables the RSpecRails/HttpStatusNameConsistency cop to enforce using
:unprocessable_content instead of the deprecated :unprocessable_entity
for HTTP 422 status codes.

Sets NewCops to disabled to prevent automatic enablement of new cops in
future gem updates, allowing us to evaluate and enable them deliberately.
@giverm giverm merged commit 4bdf8e6 into main Nov 18, 2025
6 checks passed
@giverm giverm deleted the giverm/add-rubocop-rspec_rails-gem branch November 18, 2025 17:10
@doshitan
Copy link
Contributor

doshitan commented Nov 18, 2025

@giverm is there any reason to not enable the other rspec cops from navapbc/oscer#29 in the Rails template?

@giverm
Copy link
Contributor Author

giverm commented Nov 18, 2025

@giverm is there any reason to not enable the other rspec cops from navapbc/oscer#29 in the Rails template?

@doshitan Nope, that was my misreading of one of your comments on that PR. Your comment specific to not enabling new cops, but my thinking was we'd add and enable rubocop-rspec_rails, but let downstream apps have the freedom to decide which cops to enable.

I can move the rest over the the template though. Let me know your preference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants