feat: brings back --make-paths-enum option to generate ApiPaths enum #2052
Conversation
🦋 Changeset detectedLatest commit: e4ce821 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
laurenz-glueck
force-pushed
the
feat/makePathsEnum
branch
from
d40d6ec to
9e125a9
Compare
|
@drwpow it seems you have some more context on this. I suspect the discussion in the issue went missing because it was closed. |
|
Sorry I think this was just an accidental omission for 7.x, but since it’s an opt-in feature flag I support adding it! (I’ll only try to ensure that default behavior doesn’t change). I’m in favor of this merging, but we’ll need to add a few tests just to ensure this feature doesn’t break. Also please add a |
|
@drwpow Sounds good! |
👷 Deploy request for openapi-ts pending review.Visit the deploys page to approve it
|
laurenz-glueck
force-pushed
the
feat/makePathsEnum
branch
from
e4ce821 to
4affc3c
Compare
|
@drwpow I have added a few tests and a minor changeset. |
|
|
||
| Enabling `--make-paths-enum` will add an `ApiPaths` enum like this to the generated types: | ||
|
|
||
| ::: code-group |
| }, | ||
| ], | ||
| [ | ||
| "basic with path parameter", |
Changes
Brings back
--make-paths-enumoption to generateApiPathsenum.See: #1057
Checklist
docs/updated (if necessary)pnpm run update:examplesrun (only applicable for openapi-typescript)