Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct exporting of enum classes #2126

Merged
merged 1 commit into from
Feb 16, 2016
Merged

Conversation

delenius
Copy link
Contributor

Fixes #2102.

This attaches the enum classes to the main model class. This also ensures that the enum is exported along with the model. There is no longer a need for a separate export of the enum.

The enums now looks similar to a local class in Java, which seems appropriate, since they are indeed local to the model class being defined.

Note: This conflicts with #2115
Take them in any order, and I'll rebase accordingly. We need both to really fix the enums, but the two PRs address two different issues.

@wing328
Copy link
Contributor

wing328 commented Feb 15, 2016

@delenius thanks for the PR. #2115 has been merged into master. Please kindly do a rebase on the latest master.

@delenius
Copy link
Contributor Author

@wing328 it should be fine now.

wing328 added a commit that referenced this pull request Feb 16, 2016
Correct exporting of enum classes
@wing328 wing328 merged commit 6ecf018 into swagger-api:master Feb 16, 2016
@delenius delenius deleted the enum-exports branch February 16, 2016 02:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[JavaScript] Enums are not exported correctly
2 participants