enum type properties can't be generated into models in Java

[comm604]

If a property is an enum, the Java generator doesn't create an Enum java file for it.

For example,

"Employee":
       {
           "id": "Employee",
           "description": "An employee",
           "required":
           [
               "name",
               "id"
           ],
           "properties":
           {
               "name":
               {
                   "type": "string",
                   "description": "Name of the employee"
               },
               "id":
               {
                   "type": "string",
                   "description": "Id of the employee"
               },
               "department":
               {
                   "$ref": "Department",
                   "description": "The department that the employee belongs to",
                   "enum":
                   [
                       "SALES",
                       "FINANCE",
                       "ENGINEERING",
                       "MARKETING"
                   ]
               }
           }
       }

With this example model, in addition to Employee.java, shouldn't it also generate a Department.java like the following?

public enum Department {
    SALES, FINANCE, ENGINEERING, MARKETING
}

[fehguy]

Hi, this is a new feature, marking it as such. Currently the codegen does not generate enum classes.

[RobBlairInq]

I have privately made modifications that allow this, and generate an enum inside the model class definition.
it does not use $ref, treats it like a String, but at least allows the enum items to be exposed to java.
see 1.2 swagger spec https://github.com/wordnik/swagger-core/wiki/Datatypes#complex-types for current support.

[fehguy]

This feature has been added to the java templates in 2.1.x. See the develop_2.0 branch

[adrobotics]

I'm having trouble finding the version where this is supposed to be working. The develop_2.0 branch doesn't generate any enum classes for me.

• Solved
  Java enum values must be of type string and also enclosed in "
  Ex: "status": {
  "enum": [
  "10",
  "20"
  ],
  "type": "string"
  }

[nihuyaka]

Why is this closed? As of 2.1.4 Enums are still generated inside the model which is wrong.

[fehguy]

Why? Because this ticket isn't about having external enums, it's about having enums. Making them inline is not wrong it's a style preference. I DO want to support external classes, and we're in the process of adding that support. But that's why it's closed. There's another one around external enums.

[nihuyaka]

Ah, sorry thanks.