- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: ruby-best-practices/time-now
Language: Ruby
Severity: Notice
Category: Best Practices
The rule “Prefer Time.now
over Time.new
” is a best practice in Ruby programming. Time.new
without arguments returns the current time but it’s less descriptive than Time.now
. Using Time.now
helps to improve the readability of your code by explicitly stating that you are getting the current time.
This rule is important because clear and readable code is essential for maintenance and collaboration. When other developers read your code, they should be able to understand it easily. Using Time.now
instead of Time.new
for the current time makes your code more self-explanatory.
To avoid this violation, always use Time.now
when you want to get the current time. Use Time.new
only when you need to create a time object for a specific date and time. For example, Time.new(2024, 2, 29, 12, 0, 0, "+00:00")
creates a time object for February 29, 2024, at noon UTC.
current_time = Time.new
current_time = Time.now
rule_creation_time = Time.new(2024, 2, 29, 12, 0, 0, "+00:00")
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products