Check method and parameters names for wording issues

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-inclusive/function-definition

Language: Ruby

Severity: Notice

Category: Best Practices

Description

This rule helps ensure that you adhere to naming conventions that are inclusive, clear, and unambiguous. Instead of using terms like master and slave, which have offensive connotations, use neutral and descriptive terms like primary and secondary. Names you choose should be clear, descriptive, and considerate of the diverse backgrounds of those who might read or work with your code.

Non-Compliant Code Examples

def master(slave)
end

Compliant Code Examples

def primary(secondary)
end
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

PREVIEWING: rtrieu/product-analytics-ui-changes