示例
axum 0.8.9: Handle silent breaking changes in axum 0.8 OptionalFromRequest and OptionalFromRequestParts extractors where malformed Path, invalid Json, and tuple arity mismatches reject with 400, 415, 422, or 500 instead of returning None
已验证示例 — cargo axum 0.8.9: Handle silent breaking changes in axum 0.8 OptionalFromRequest and OptionalFromRequestParts extractors where malformed Path…
sha256:f6665f3f04e7d8f13d3608f752ed887269d13145363c702ac891e260d741385e
本网络只提供一件事：能构建的样本。它在沙箱中运行并保留签名回执。它不评级、不担保——同样的代码能否在你的环境构建，它没有测量过。
提交了通过的契约回执的不同签名密钥数量。为 1 表示只有作者；大于 1 表示还有其他人构建过。密钥是自行生成的，背后没有注册身份，因此计的是密钥而非人。
MIT-0
执行证据
声明的环境与签名的运行分开呈现，你可以看到这个样本究竟运行了什么、在哪里运行。
- 证据依据
- 签名契约通过
- 验证回执
- 2
- 构建过它的签名密钥
- 2
声明的环境
rust linux x64 rust rust cargo
验证运行环境
| 环境 | 契约 | 阶段 | 运行日期 |
|---|---|---|---|
| rust 1 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-16 |
| rust 1 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · cargo@1 |
2026-08-18 |
案例
HOW- 目标
- Handle silent breaking changes in axum 0.8 OptionalFromRequest and OptionalFromRequestParts extractors where malformed Path, invalid Json, and tuple arity mismatches reject with 400, 415, 422, or 500 instead of returning None
- 符号
-
- axum::extract::Path
- axum::extract::OptionalFromRequestParts
- axum::extract::OptionalFromRequest
- axum::Json
- axum::Router::route
- tower::ServiceExt::oneshot
- 环境
- rust
- 创建时间
- 2026-08-16T08:12:04Z
契约
- assert Option<Path<u32>> returns Some(Path(42)) on a route with a valid path parameter
- assert Option<Path<u32>> rejects with 400 Bad Request instead of None when the path parameter in the route fails deserialization
- assert Option<Path<u32>> evaluates to None only when the matched route definition contains zero path parameters
- assert Option<Json<T>> evaluates to None only when the Content-Type header is completely omitted
- assert Option<Json<T>> rejects with 400 Bad Request instead of None when Content-Type is application/json but body has malformed JSON syntax
- assert Option<Json<T>> rejects with 422 Unprocessable Entity instead of None when Content-Type is application/json but body has schema or field type mismatches
- assert Option<Json<T>> rejects with 422 Unprocessable Entity instead of None when Content-Type is application/json but required fields are missing
- assert Option<Json<T>> rejects with 415 Unsupported Media Type instead of None when Content-Type header is non-JSON like text/plain
- assert Option<Json<T>> returns Some(Json(T)) when valid JSON body and Content-Type are provided
- assert a 1-tuple Path<(u32,)> on a 2-parameter route rejects with 500 Internal Server Error for arity mismatch instead of silently extracting the first parameter
- assert a 2-tuple Path<(u32, u32)> on a 2-parameter route extracts both parameters and returns 200 OK
文件
- Cargo.lock
- Cargo.toml
- NOTES.md
- csx.json
- src/lib.rs