Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Currently I am using nestjs swagger to createn open api spec, and then this repo to create types for the client.

This works surprisingly well, except when it comes to enums. OpenAPI strips away the info needed to make a good enum and now I am unhappy with the difference between client/server when it comes to how the type is defined.

I don't have a solution other then sharing the enum, but then I can't use the types this repository generates (because it won't match). How do you solve this?

You must be logged in to vote

Replies: 1 comment

Comment options

Enums are a planned upcoming edition to this library! It’s been a common ask, and a couple people have expressed interest in opening a PR to make this happen. I will get to it eventually if no one else does. Either way, will tag this discussion when a PR opens up adding this and will request feedback to see if it’s a good path forward or not.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.