This product is not supported for your selected Datadog site. ().
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다. 현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
Metadata
ID:ruby-best-practices/avoid-hash-constructor
Language: Ruby
Severity: Notice
Category: Best Practices
Description
The “Use hash literal” rule in Ruby encourages the use of hash literals, {a => b, c => d}, instead of the Hash[] method for creating hashes. This rule is crucial because hash literals are more readable, straightforward, and faster in performance compared to the Hash[] method.
The Hash[] method might be less clear to some developers, especially those new to Ruby, because it’s not immediately obvious that a hash is being created. Moreover, the Hash[] method is slower because it involves method call overhead, which can impact the performance of your application if used extensively.
To adhere to this rule, always use hash literals when creating a new hash. For example, instead of using Hash[a, b, c, d], use {a => b, c => d}. Similarly, if you need to convert an array to a hash, instead of using Hash[ary], use ary.to_h. This will enhance readability and performance of your code.
Non-Compliant Code Examples
Hash[ary]Hash[a,b,c,d]
Compliant Code Examples
ary.to_h{a=>b,c=>d}
원활한 통합. 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 검사를 추가합니다