Path-level parameters are ignored
A path parameter declared once at path level was absent from generated handler types and unavailable to runtime parameter handling.
This page traces one detailed external-report case through the available source and release evidence. The public-record census includes additional discovery channels and separately identified recurrences.
- Report
- Issue #1971
- Reporter
- dissemond-bitside
- Reported
- April 30, 2026
- Reported version
- 2.10.0
- Matched window
- Included
- First affected release entered matched window
- No
- Origin classification
- Pre-existing before 2026
- Classification confidence
- High
- Chronology confidence
- High
- Accepted correction
- PR #1972
- First fixed release
- 2.11.0
- Report to release
- 4.93 elapsed daysReport: 2026-04-30T01:54:48Z; corrected publication: 2026-05-05T00:10:50.946Z.
Historical test demonstration and reproducible commands
Finding
The omission is visible in the earliest parameter-generation implementation from 2022 and remained present through 2025.
Evidence trail
Origin
Exact origin: 193bc9b0, committed July 12, 2022; first affected release 0.5.0. Parameter collection read only operation-level arrays and never merged parameters declared on the enclosing Path Item.
Source history and behavioral evidence
Historical source consistently reads operation.parameters without incorporating pathItem.parameters. The fix merges both scopes with the OpenAPI-required operation-level override semantics and covers generator and runtime behavior.
Release chronology
The omission exists by 0.5.0. The correction shipped in 2.11.0 five days after the report.