Sync OpenAPI specification for (spec-v1-synthetics.yaml) #2214
Conversation
| @@ -1536,7 +1536,7 @@ def list_global_variables_with_http_info(opts = {}) | |||
| return_type = opts[:debug_return_type] || 'SyntheticsListGlobalVariablesResponse' | |||
|
|
|||
| # auth_names | |||
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth, :AuthZ] | |||
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth, :AuthZ, :AuthZ] | |||
There was a problem hiding this comment.
⚪ Code Quality Violation
| auth_names = opts[:debug_auth_names] || [:apiKeyAuth, :appKeyAuth, :AuthZ, :AuthZ] | |
| auth_names = opts[:debug_auth_names] || %i[apiKeyAuth appKeyAuth AuthZ AuthZ] |
Consider using the %i syntax instead (...read more)
The rule "Prefer %i to the literal array syntax" is a guideline that encourages the use of the %i syntax for arrays of symbols. This is a part of the Ruby style guide that aims to promote conciseness and readability.
Symbols are immutable, reusable objects often used in Ruby instead of strings when the value does not need to be changed. When declaring an array of symbols, using the %i syntax can make your code cleaner and easier to read.
To adhere to this rule, instead of declaring an array of symbols using the literal array syntax like [:foo, :bar, :baz], use the %i syntax like %i[foo bar baz]. It's a good practice to consistently use %i for arrays of symbols as it enhances code readability and maintainability.
Datadog ReportBranch report: ✅ 0 Failed, 1040 Passed, 1903 Skipped, 1m 48.04s Total duration (59.01s time saved) |
12c7976 to
75b01a6
Compare
75b01a6 to
9cb86b4
Compare
See DataDog/datadog-api-spec#3452
Test branch datadog-api-spec/test/sync-forwarder-specs/488ea684536e2f3b4cb32e40f64e791c-spec-v1-synthetics.yaml