- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: ruby-code-style/yield-self-to-then
Language: Ruby
Severity: Notice
Category: Best Practices
The rule “Prefer using then
over yield_self
” is a coding practice in Ruby that helps improve code readability and simplicity. In Ruby, both yield_self
and then
are used to yield the receiver to a block and return the result. However, as of Ruby 2.6, then
is the preferred method due to its simplicity and clearer syntax.
The importance of this rule lies in the maintenance and readability of the code. then
is more intuitive and easier to understand for developers, especially those who are new to Ruby. This can lead to fewer misunderstandings and bugs in the code, and make it easier for developers to read and maintain the code in the future.
To follow this rule, replace any instances of yield_self
with then
. For example, instead of writing foo.yield_self { |x| x.do_something }
, you should write foo.then { |x| x.do_something }
. Similarly, "FOO".yield_self { |x| x.downcase }
should be replaced with "FOO".then { |x| x.downcase }
.
foo.yield_self { |x| x.do_something }
"FOO".yield_self { |x| x.downcase }
foo.then { |x| x.do_something }
"FOO".then { |x| x.downcase }
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products