Fix Ruby-version-dependent hash literal syntax in generated specs

[dblock]

Problem

The scheduled automated API update workflow (PR #578 being an example) occasionally produced spurious diffs flipping hash literal syntax back and forth between:

{data: ["data"]}

and

{:data=>["data"]}

Root cause

Ruby 3.4 changed Hash#inspect's default rendering of symbol keys from the hash-rocket form (:foo=>1) to the modern shorthand (foo: 1). lib/slack/web/api/templates/method_spec.erb relied on implicit string interpolation of a real Hash object (#{val}) when building the "encodes ... as json" test's params, so the literal syntax emitted into generated spec files depended on whichever Ruby version ran the generator. .github/workflows/update_api.yml's scheduled job pins Ruby 3.2, while a contributor running the rake task locally may have a newer Ruby, so regenerated PRs would alternate style depending on who/what last ran it.

Fix

Add a ruby_literal helper to method_spec.erb that explicitly renders Hash/Array values as source text using the modern key: value syntax (valid since Ruby 1.9, well within this gem's supported Ruby 2.7+ range) instead of relying on Hash#inspect. This makes generated output deterministic and independent of the Ruby version used to run rake slack:web:api:update.

Verified by regenerating all endpoints/specs/commands with this template change: only the fix itself changed (no other endpoint or spec file differs), confirming the current master content already matches this deterministic format and future regenerations will no longer drift.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[github-actions]

Danger Report

No issues found.

View run

[coveralls]

Coverage Report for CI Build 28751995911

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage remained the same at 91.075%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	5759
Covered Lines:	5245
Line Coverage:	91.07%
Coverage Strength:	110.66 hits per line

---

💛 - Coveralls