I agree with your insight and always try to follow OAS standards.
The reason for introducing this tool is that TypeScript's openapi-generator is immature, so many front-end developers read and write interaction code by themselves without automating SDK generation.
Of course, as @nestia/migrate is not matured yet, it could be another immature SDK generator for someone's insight \o/.
You may try "npm init rpc", it's also generate client sdk based on server implementation. You don't need to specific the interface in multiple places with it.
I use the create-* package to generate the skeleton of backend server, and it generates the typescript client on the fly.
I can then use the client sdk in SPA (angular or react).
I know there are at least 10+ e-commerce projects based on this design (booking, office automation, e-shop, e.t.c.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree with your insight and always try to follow OAS standards.
The reason for introducing this tool is that TypeScript's
openapi-generatoris immature, so many front-end developers read and write interaction code by themselves without automating SDK generation.Of course, as
@nestia/migrateis not matured yet, it could be another immature SDK generator for someone's insight \o/.Have you tried swagger-typescript-api?
You may try "npm init rpc", it's also generate client sdk based on server implementation. You don't need to specific the interface in multiple places with it.
That's interesting. Do you use it for something? What does it make under the hood actually? The package and repo look quite weird and obscure.
I use the create-* package to generate the skeleton of backend server, and it generates the typescript client on the fly.
I can then use the client sdk in SPA (angular or react).
I know there are at least 10+ e-commerce projects based on this design (booking, office automation, e-shop, e.t.c.)