swagger-api / swagger-api/swagger-codegen
Generation into multiple output directories
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
For C, C++, Objective-C, etc we usually split the public interface from the implementation. Example: Public header files should go to include, private header files (eg. for helpers) and implementation files should go to src.
In the generator, I can add multiple entries to modelTemplateFiles. Each entry may have a different extension, but I also need to specify a different prefix.
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 tracing how the generator handles modelTemplateFiles and how output paths or prefixes are assigned for each entry. Verify the generated layout for a language with public and private files: public headers should go to include, while private headers and implementations should go to src, with distinct prefixes supported per template entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp, objective-c
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100