[dinwwwh]

Requested by dinwwwh · project thread

Summary

Zod's z.base64().nullable() writes anyOf: [{ type: "string", contentEncoding: "base64", pattern: "..." }, { type: "null" }]. The downgrader turns it into { type: "string", format: "byte", pattern: "...", nullable: true }, as designed.

OpenAPI Generator 7.26's rust-axum server checks a format: byte pattern with a generated validate_byte_* function that takes &ByteArray. A nullable property's field is a Nullable<ByteArray>, so the model does not compile:

error[E0308]: mismatched types
expected `&ByteArray`, found `&Nullable<ByteArray>`

This adds one sentence to the existing note on OpenAPI Generator's Rust client and Spring server.

What was checked

Each shape was compiled with cargo build from both the 3.1 input and the downgraded 3.0 output:

Shape	3.1	3.0
required nullable base64 with pattern	ok	fails
optional nullable base64 with pattern	ok	fails
array of nullable base64 with pattern	ok	ok
required/optional non-null base64 with pattern	ok	ok
required/optional nullable base64 without pattern	ok	ok
nullable string with a pattern but no byte format	ok	ok

Only README text changes. uncheck passes.

---

Generated by Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed]

Merging this PR will not alter performance

1 warning

⚠️ 1 benchmark is dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

✅ 29 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing claude/project-thread-fvev8j (95b5cee) with main (e1af7bb)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[pullfrog]

✅ No new issues found.

Reviewed changes

• OpenAPI Generator rust-axum nullable byte + pattern note — adds one clause to the existing OAG bullet in packages/downgrader/README.md: in 7.26 the Rust server generator (rust-axum) does not compile a nullable format: byte property, required or optional, that also carries a pattern, as Zod's z.base64() writes.

I checked the load-bearing claim against OAG v7.26.0: in rust-axum/models.mustache an isByteArray property with a pattern emits custom(function = "validate_byte_<class>_<prop>"), whose signature is fn(&ByteArray), while the field is typed Nullable<ByteArray> (required) or Option<Nullable<ByteArray>> (optional) — and ModelUtils.isByteArraySchema matches format: byte, so the branch is reached. The custom validation is emitted outside the {{^isNullable}} guard (unlike the XSS checks), which is exactly the reported E0308. Since the PR's own table shows non-null optional byte + pattern compiles, validator unwraps Option and passes the inner type, so the Nullable<ByteArray> case is what mismatches. The Zod-writes-a-pattern premise is also already documented in the repo's ogen note. uncheck passes for the file.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}