Cette page n'est pas encore disponible en français, sa traduction est en cours. Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
The rule requires that the exception class and the message be separated in the raise statement. This is important because it makes the code more readable and easier to understand. It also helps to avoid potential syntax errors or unexpected behavior.
When you combine the exception class and the message into a single object, it can be confusing to other developers who are trying to understand your code. It may not be immediately clear what type of exception is being raised, or what the associated message is.
To comply with this rule, separate the exception class and the message with a comma when you raise an exception. For example, instead of writing raise SomeException.new('message'), you should write raise SomeException, 'message'. This makes it clear that you are raising a SomeException and that the associated message is ‘message’. It also makes your code more consistent with common Ruby coding conventions.
Non-Compliant Code Examples
raiseSomeException.new('message')
Compliant Code Examples
raiseSomeException,'message'
Seamless integrations. Try Datadog Code Analysis
Datadog Code Analysis
Try this rule and analyze your code with Datadog Code Analysis
How to use this rule
1
2
rulesets:- ruby-best-practices # Rules to enforce Ruby best practices.
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
