swagger-api/swagger-codegen

codegen doesn't take into account the default values

Open

#1,892 opened on Jan 14, 2016

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

Description

Hi,

Here is my swagger description:

  inline_response_200:
    properties:
      surname:
        type: "integer"
        default: 1
        format: "int32"
      name:
        type: "string"
        default: "lazy"
        enum:
        - clueless
        - lazy
        - adventurous
        - aggressive

And that's what we receive in the generated nodejs app:

exports.newCustomer = function(request) {

  var examples = {};

  examples['application/json'] = {
  "name" : "aeiou",
  "surname" : 123
};

Is that ok, that default values are not taken into consideration? string is the same each time, the numer also the same. Is that possible to make it work? As we don't want to use hardcoded examples.

Regards,

Contributor guide

Tech stack
javanodejs
Domain
backendapi
Issue type
bug
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-3 hours
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.
clear
Prerequisites
understand swagger codegen templatesknow how default values work in swagger
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the code generation templates for Node.js (likely in modules/swagger codegen/src/main/resources/handlebars/NodeJS). Look for how example values are generated from the swagger spec, specifically whether default values from the schema are being ignored. Check if there is any logic to fallback to default when examples are not provided. The issue has 3 comments that may contain additional hints about the root cause. A fix would involve modifying the template to include default values when generating example responses.
codegen doesn't take into account the default values · swagger-api/swagger-codegen#1892 | Good First Issue