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'
원활한 통합. Datadog Code Security를 경험해 보세요
Datadog Code Security
이 규칙을 사용해 Datadog Code Security로 코드를 분석하세요
규칙 사용 방법
1
2
rulesets:- ruby-best-practices # Rules to enforce Ruby best practices.
리포지토리 루트에 위의 내용을 포함하는 static-analysis.datadog.yml을 만듭니다
무료 IDE 플러그인을 사용하거나 CI 파이프라인에 Code Security 검사를 추가합니다
