Check comments for wording issues

Documentos > Code Analysis > Static Analysis Rules > Check comments 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/comments

Language: Ruby

Severity: Notice

Category: Best Practices

Description

This rule checks the comments in your Ruby code for potentially insensitive or inappropriate wording. It specifically flags terms considered problematic due to historical connotations.

To avoid violating this rule, use neutral, descriptive terms in your comments. For example, instead of using “master”, you could use terms like “primary”, “main”, or “leader”.

Non-Compliant Code Examples

# master
print("foo")

Compliant Code Examples

# primary
print("foo")

How to use this rule

1
2
rulesets:
  - ruby-inclusive     # Rules to enforce Ruby inclusive.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products