示例
Handle Faraday JSON response deserialization and error middleware ordering without unparsed string payloads or type mutation traps
sha256:dfee68bbd326424c9c702d0cf42e9ddcaf36879dbd2f497a522dcfbc402a3938
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Handle Faraday JSON response deserialization and error middleware ordering without unparsed string payloads or type mutation traps HOW
- 包
- faraday 2.14.3
- 环境
- ruby
- 创建时间
- 2026-08-17T02:38:41Z
常见的想当然
Declaring response :json before response :raise_error in a Faraday connection ensures 4xx and 5xx error response bodies are deserialized into Ruby Hashes on rescued client and server exceptions.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- Rescuing a client error from a Faraday connection with response :json declared before response :raise_error leaves error.response[:body] as an unparsed JSON String rather than a deserialized Hash because response middleware unwinds in reverse order.
- Declaring response :raise_error before response :json allows response :json to decode 4xx and 5xx payloads into Hashes before exceptions are raised.
- Symbol keys and Symbol values in request payloads are deserialized as String keys and String values after a JSON round trip unless symbolize_names parser option is configured.
- Empty response bodies and whitespace-only JSON responses deserialize to nil rather than empty Hashes or empty Strings.
- Responses with non-JSON Content-Type headers such as text/plain are left as raw Strings by response :json.
- Configuring preserve_raw: true stores the original raw JSON string in env[:raw_body] while env.body holds the parsed Hash.
文件
- Gemfile
- Gemfile.lock
- NOTES.md
- csx.json
- src/client.rb
- test/contract.rb
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- ruby 3 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · rubygems@1 · 2026-08-17 · ed25519:d91480838ac982c9