Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raise severity of some cops to warning #204

Merged
merged 1 commit into from Jan 9, 2023

Conversation

koic
Copy link
Member

@koic koic commented Dec 17, 2022

The cops below belong to linting, not style preference, so make set the severity to warning.

The following emulates warnings for deprecated APIs:

The following suggests incorrect usage of APIs:

  • Minitest/AssertRaisesWithRegexpArgument:
  • Minitest/AssertWithExpectedArgument:
  • Minitest/SkipEnsure:
  • Minitest/UnreachableAssertion:

Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

The cops below belong to linting, not style preference,
so make set the severity to warning.

The following emulates warnings for deprecated APIs:

- Minitest/GlobalExpectations (rubocop#60)

The following suggests incorrect usage of APIs:

- Minitest/AssertRaisesWithRegexpArgument:
- Minitest/AssertWithExpectedArgument:
- Minitest/SkipEnsure:
- Minitest/UnreachableAssertion:
@koic koic merged commit 02f30f3 into rubocop:master Jan 9, 2023
@koic koic deleted the raise_severity_of_some_cops_to_warning branch January 9, 2023 10:33
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.

None yet

1 participant