[Objective-C] Code generator is not creating enums

[MrMatthewDavis]

Enums defined in json models get codegen'd as NSString properties, and no enums are created. This can be observed in the petstore example, which has enum properties but don't get translated in the objective-c codegen.

[wing328]

@mad102190 yes, enum is not supported in ObjC at the moment. Do you have cycle to help implement it for ObjC client? You can find enum-related mustache tag in https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-codegen/src/main/resources/Java/enumClass.mustache (Java client).

[wing328]

@mad102190 by the way, for #971 if you need help with the rebase or the integration test with the ObjC client, please let me know (and thanks again for the PR to add the support of status code and HTTP response header)

FYI. We (the community) have implemented similar feature via #1127 for Java and C# client.

[MrMatthewDavis]

@wing328 I've submitted a PR that enables support for enums in Objective-C, so we can close this issue once the PR is merged in. As for #971, did we not determine that there could be possible concurrency issues with the responseHeaders property if running on multiple threads? If that's not a problem, I can rebase and re-open the PR. Let me know. I'll take a look at the C# and Java implementation and see how the thread concurrency issue was addressed there.

[wing328]

@mad102190 it would be a problem if the developer is using the same ApiClient across all threads. The recommended way is to use an instance of ApiClient per thread (same for C# and Java)

[MrMatthewDavis]

That makes perfect sense. I'll work on rebasing that today.

On Sep 3, 2015, at 7:45 AM, wing328 notifications@github.com wrote:

@mad102190 it would be a problem if the developer is using the same ApiClient across all threads. The recommended way is to use an instance of ApiClient per thread (same for C# and Java)

—
Reply to this email directly or view it on GitHub.

[wing328]

@mad102190 take your time. Once again appreciate your contribution to the project.

[MrMatthewDavis]

@wing328 No problem, thank you for being so helpful! I've created a brand new PR for the response headers. Please see #1189.

[fehguy]

I think that what we want is different from enum types. If you take an example like such:

definitions:
  Example:
    type: string
    enum:
      - First
      - Second

We could easily create an enum class:

typedef NS_ENUM(NSInteger, Example) {
    First, Second
};

But what we really want is a NSString which has the acceptable values of First, Second. Thus creating an enum class is actually a bit odd for the codegen. If you, for example, referenced the enum in another model:

  Example2:
    # references an enum class
    type: object
    properties:
      status:
        $ref: '#/definitions/Example'

What would you expect the payload to be? I'm thinking this:

{
  "status": "First"
}

Am I missing something?