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
String#to_time
Reference: https://rails.rubystyle.guide/#to-time
I have the code:
# frozen_string_literal: true class User < ApplicationRecord def method '2015-03-02 19:05:37'.to_time end end
I will run rubocop and not get any offenses:
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:
[Fix rubocop#1094] Make Rails/TimeZone aware of String#to_time
Rails/TimeZone
49560be
Fixes rubocop#1094. This PR make `Rails/TimeZone` aware of `String#to_time`.
Merge pull request #1096 from koic/make_rails_time_zone_aware_of_stri…
8e43737
…ng_to_time [Fix #1094] Make `Rails/TimeZone` aware of `String#to_time`
Successfully merging a pull request may close this issue.
Reference: https://rails.rubystyle.guide/#to-time
Actual behavior
I have the code:
I will run rubocop and not get any offenses:
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: