swagger-api/swagger-codegen

review success, other response types

Open

#591 opened on Apr 5, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Issue: Bughelp wanted

Description

from https://github.com/swagger-api/swagger-codegen/pull/366

Contributor guide

Tech stack
java
Domain
backendapi
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.
1-2 days
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.
unclear
Prerequisites
Understanding of Swagger/OpenAPI specificationBasic knowledge of Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
This issue requests adding support for additional response types (e.g., success responses beyond the default) in the code generator. The linked PR #366 may provide context for the expected implementation. To start, examine how existing response types are handled in the template files and the generator logic in the Java source code.