OpenAPITools / OpenAPITools/openapi-generator
[core] Tracking item: add GlobalFeature.ParameterizedServerPerOperation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
I was not clear. There are actually 2 features to track:
- Support for global server configuration with templated values (all Java)
- Support for server configuration per endpoint (only jersey2, go-experimental)
Originally posted by @jirikuncar in https://github.com/OpenAPITools/openapi-generator/pull/5380
While we have a feature indicating "Global" parameterized server support, we should also have a feature which indicates the ability to parameterize a server for a given operation. Example use case would be multi-tenant APIs where username/account may indicate a different server rather than a different resource on the same server as in REST.
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
Start by reviewing the existing global parameterized-server feature and PR 5380, then compare the two tracked capabilities: templated global server configuration and per-operation server configuration. Check the jersey2 and go-experimental support mentioned in the issue; done should mean the intended GlobalFeature.ParameterizedServerPerOperation indicator and its scope are clearly defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100