-
-
Notifications
You must be signed in to change notification settings - Fork 395
New fork swagger-typescript-api-nextgen
with extra features and fixes
#360
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
Comments
Is there a reason these changes aren't a PR for swagger-typescript-api project? |
@andersfylling PR for a long time aren't accepted, the project seems to be abandoned. |
Looks like recently, activity is returning to this repo. Maybe this would be a good time to have the changes merged back into this original repo? |
Hi @grandsilence , your fork looks good ! |
Hi @js2me, I am currently using the nextgen package, but would love to switch back to the original one. That being said, the main reason I started using the templates/base/http-clients/axios-http-client.eta
For my project, not using {
"compilerOptions": {
"preserveValueImports": true,
"importsNotUsedAsValues": "error",
}
} These are default (and I believe encessary) options for Vite + Vue projects. Is there any chance this could make it into one of the following versions? |
Please check out my fork: swagger-typescript-api-nextgen, maybe it will be useful for those who need a secure version with updated dependencies, as well as support for current axios and other fixes.
The package is present in the npm (swagger-typescript-api-nextgen).
✨ The fork key differences
next
tomaster
and some commits from origin pull requests:title
of object type (fix: fix missingtitle
of object type #303)The text was updated successfully, but these errors were encountered: