OpenAPITools / OpenAPITools/openapi-generator
[BUG] [Rust Server] Not support operationId blank separator issue.
Open
Nobody has claimed this yet.
Issue: Bug
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- What's the version of OpenAPI Generator used?
- Have you search for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Bounty to sponsor the fix (example)
Description
Not support operationId-blank separator issue.
openapi-generator version
OpenAPI declaration file content or url
modules/openapi-generator/src/test/resources/3_0/rust-server/openapi-v3.yaml
get:
tags: [Repo, Info]
operationId: Get Repo\Info
Command line used for generation
bin/rust-server-petstore.sh
Steps to reproduce
Run the generated code openapi-v3/
Related issues/PRs
No
Suggest a fix
- Add replace(" ", "") after camelize(operationId) to eliminate blank.
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 with modules/openapi-generator/src/test/resources/3_0/rust-server/openapi-v3.yaml and bin/rust-server-petstore.sh, then inspect how the Rust server generator handles the operationId Get Repo\Info. Run the generation command and the generated openapi-v3/ server; done means the operationId no longer produces a blank separator in the generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100