swagger-api/swagger-codegen

Update importMapping with proper mapping between model and package

Open

#3,455 opened on Jul 26, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Enhancement: Featurehelp wanted

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

Tech stack
java
Domain
toolingbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaMustache templatingSwagger codegen internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the importMapping variable in the swagger codegen generator Java code. Look for how it is set and passed to Mustache templates. Identify the template files for C# and Ruby generators (e.g., in modules/swagger codegen/src/main/resources/handlebars/ or mustache directories) and add the importMapping to the template context if missing. Check similar generators for reference.