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

Fix an error for Lint/UselessTimes when no block is present #12775

Merged
merged 1 commit into from Mar 11, 2024

Conversation

Earlopain
Copy link
Contributor

Another thing that's more common with an LSP.


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.

@bbatsov bbatsov merged commit eceedb7 into rubocop:master Mar 11, 2024
33 checks passed
@Earlopain Earlopain deleted the fix-error-for-lint-useless-times branch March 11, 2024 10:04
@@ -292,6 +292,15 @@ def my_method

expect_no_corrections
end

it 'registers no offense for 1.times without block' do
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does register an offense, though?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, right. Initially my intention was to not register something but I switched it up without updating this as well.

I'll try my hand at maybe making/extending some internal affair for this, there are already things that check for correct spec titles.

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

3 participants