swagger-api / swagger-api/swagger-codegen
Update importMapping with proper mapping between model and package
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently, importMapping is not utilized in some generators (e.g. C#, Ruby, etc) since the importMapping is not used in the mustache template.
We still want to maintain a proper mapping between model/type and package/module in case developers customizing the generator need access to the mapping.
Swagger-codegen version
2.2.1
Suggest a Fix
If anyone from the community wants to contribute on this, please reply to let us know. Thank you.
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 locating how importMapping is built and where the C# and Ruby generator templates consume or omit it. Compare the model/type-to-package/module mapping across generators and verify that customized generators can access the mapping when the affected templates are rendered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100