OpenAPITools / OpenAPITools/openapi-generator
[REQ] Even if URL path starts with server port , openapi-generator can work well (version 4.1.3)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Is your feature request related to a problem? Please describe.
I found that og(openapi-generator) version 3.1.1-SNAPSHOT can generate PYTHON client code if the path contains port, like ":11180/a/b/c".
But version 4.1.3 reports a error : -attribute paths. Resource :11180/a/b/c should start with / .
Describe the solution you'd like
What I want is that the higher version can be backward compatible.
In other words, the version 4.1.3 can also generate PYTHON client code without any error even if the URL path starts with server port such as :1000/a/b/c.
Is there a switch to turn off the test?
Describe alternatives you've considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with an OpenAPI document whose path is :1000/a/b/c using version 4.1.3, and compare it with 3.1.1-SNAPSHOT. Trace the path validation used before Python client generation; done means the compatibility behavior is defined and covered by a regression test without unintentionally weakening validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100