- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
ID: ruby-best-practices/isa-over-kindof
Language: Ruby
Severity: Notice
Category: Best Practices
The rule “Prefer is_a?
over kind_of?
” suggests to use the method is_a?
instead of kind_of?
in your Ruby code. Both is_a?
and kind_of?
methods check if an object is an instance of a class or its subclasses. However, is_a?
is generally preferred due to its clear and concise terminology.
This rule is important for maintaining consistency and readability in your code. Using is_a?
makes your code more understandable to other developers because its function is immediately apparent from its name. On the other hand, kind_of?
might lead to confusion as it’s not as clear in its function.
To avoid this rule violation, always use the is_a?
method when you want to check the class of an object. For example, instead of writing something.kind_of?(Array)
, you should write something.is_a?(Array)
. This will make your code easier to read and understand, leading to better maintainability and fewer bugs.
something.kind_of?(Array)
something.is_a?(Array)
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products