Skip to content

Conversation

@Earlopain
Copy link
Contributor

Rubocop already defined its own blank? method (🙁), so ruby always warns when it is loaded again.

There's no real point in using the extension though, so just not using it seems ideal.


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.
  • If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Rubocop already defined its own `blank?` method (🙁),
so ruby always warns when it is loaded again.

There's no real point in using the extension though, so just not using it seems ideal.
@koic koic merged commit 8056bdc into rubocop:master Mar 15, 2025
16 checks passed
Earlopain added a commit to Earlopain/rubocop-rails that referenced this pull request May 7, 2025
…mment is passed as a local variable

To do that, be more specific about what type you expect to call blank? on (strings only).

Caused by rubocop#1467
Earlopain added a commit to Earlopain/rubocop-rails that referenced this pull request May 8, 2025
…mment is passed as a local variable

To do that, be more specific about what type you expect to call blank? on (strings only).

Caused by rubocop#1467
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.

2 participants