We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reference: https://rails.rubystyle.guide/#where-ranges
I have the code:
# frozen_string_literal: true class User < ApplicationRecord def method # bad User.where('created_at >= ?', 30.days.ago).where('created_at <= ?', 7.days.ago) User.where('created_at >= ? AND created_at <= ?', 30.days.ago, 7.days.ago) User.where('created_at >= :start AND created_at <= :end', start: 30.days.ago, end: 7.days.ago) # bad User.where('created_at >= ?', 7.days.ago) end end
I will run rubocop and not get any offences:
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop app/models/user.rb Inspecting 1 file . 1 file inspected, no offenses detected
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop -V 1.55.1 (using Parser 3.2.2.3, rubocop-ast 1.29.0, running on ruby 2.7.8) [x86_64-linux] - rubocop-capybara 2.18.0 - rubocop-factory_bot 2.23.1 - rubocop-performance 1.18.0 - rubocop-rails 2.20.2 - rubocop-rake 0.6.0 - rubocop-rspec 2.23.0 - rubocop-thread_safety 0.5.1
The text was updated successfully, but these errors were encountered:
This proposal is a dup with #689.
Sorry, something went wrong.
No branches or pull requests
Reference: https://rails.rubystyle.guide/#where-ranges
Actual behavior
I have the code:
I will run rubocop and not get any offences:
Rubocop
ydakuka@yauhenid:~/Work/project$ bin/rails_docker rubocop -V 1.55.1 (using Parser 3.2.2.3, rubocop-ast 1.29.0, running on ruby 2.7.8) [x86_64-linux] - rubocop-capybara 2.18.0 - rubocop-factory_bot 2.23.1 - rubocop-performance 1.18.0 - rubocop-rails 2.20.2 - rubocop-rake 0.6.0 - rubocop-rspec 2.23.0 - rubocop-thread_safety 0.5.1
The text was updated successfully, but these errors were encountered: