Bug: openapi parameter order doesn't match the order in the path
Description
Unconsumed parameters appear to be added last to the openapi spec, which causes strange parameter ordering in other generated code. It looks like some effort was made to account for this at https://github.com/litestar-org/litestar/blame/ffaf5616b19f6f0f4128209c8b49dbcb41568aa2/tests/unit/test_openapi/test_schema.py#L613. I'm wondering if this is really the desired behavior. I would have expected the order in the openapi spec to match the order in the path. As it stands, it means that consuming a dependency will change the openapi spec and code generated from it.
URL to code causing the issue
No response
MCVE
No response
Steps to reproduce
No response
Screenshots
No response
Logs
No response
Litestar Version
2.9.1
Platform
- Linux
- Mac
- Windows
- Other (Please specify in the description above)
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too