| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-29 | 1.7 kB | |
| v1.2.0 source code.tar.gz | 2026-09-29 | 210.2 kB | |
| v1.2.0 source code.zip | 2026-09-29 | 246.1 kB | |
| Totals: 3 Items | 458.1 kB | 0 | |
OpenAPI v1.2.0
OpenAPI v1.2.0
New features
- Generated server handlers can return
OpenAPI.Reply(status, body)to pick a documented response status explicitly. The body is still validated and encoded against that response. Resolution order is exact status, then range (4XX), thendefault; an undocumented status is a server error. Plain return values and rawHTTP.Responsereturns behave as before. (#129, fixes [#119])
Performance
- Schema validation cuts per-node bookkeeping. On a large benchmark document, decoding with
validate = trueis about 3.6× faster (5.72 s → 1.57 s), and decoding without validation is about 2× faster. What is accepted or rejected does not change. (#126)
Compatibility
- Newly generated clients and servers target generated-code contract 4. The runtime accepts contracts 3 and 4, so existing generated modules keep loading and keep their behavior without regeneration. Regenerate a server to use
OpenAPI.Reply. - Contract-4 modules need OpenAPI.jl 1.2 or later, and older runtimes reject them at load time. Packages that commit generated output should declare
OpenAPI = "1.2"compat. - Generated server stubs no longer put a
-> ReturnTypeon the handler signature comments.
Merged pull requests:
- perf(schema_engine): cut per-node bookkeeping from compiled validation (#126) (@jd-lara)
- Drop unused MbedTLS dependency (0.2.10) (#127) (@krynju)
- Validate generated server replies with explicit status codes (#129) (@quinnj)
- increment minor version to 1.2.0 (#130) (@tanmaykm)
Closed issues:
- Deal with different success responses (#119)