This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

ID: ruby-code-style/yield-self-to-then

Language: Ruby

Severity: Notice

Category: Best Practices

Description

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 }.

Non-Compliant Code Examples

foo.yield_self { |x| x.do_something }
"FOO".yield_self { |x| x.downcase }

Compliant Code Examples

foo.then { |x| x.do_something }
"FOO".then { |x| x.downcase }
https://static.datadoghq.com/static/images/logos/github_avatar.svg https://static.datadoghq.com/static/images/logos/vscode_avatar.svg jetbrains

Seamless integrations. Try Datadog Code Analysis