jnwltr
Added support for enum definitions. Improves usage of reusable enums.
I have added the generation of enum definition types. Empty files were generated for enum types.
Thank you for the PR!
Please add a suitable example to the demo-app/client/swagger-files/unit-test-swagger.json and generate the test files. Thanks!
Thank you for the PR!
Please add a suitable example to the demo-app/client/swagger-files/unit-test-swagger.json and generate the test files. Thanks!
@fazpu, @jnwltr I extended the UserDetails definition with gender as an example enum in the demo-app. Is it possible to review? Thanks.
I have some issues with this fork compared to v4.1.0. Other than the enums, it renames some methods, such that they conflict. I have the GET methods approval and approval/count, before the generated names were approval and count. Now they are both getItems, which they share in the OpenApi definition, but no good to use due to conflict. Maybe the path could also conflict, in which case the naming strategy should look at both.
Also, for the enums, you can simply cast them as const instead of the enum type. This give them stricter type safety with less effort.
@wvpelt sorry for making you wait so long, and thanks a lot for the PR. Anyway, if you were able to rebase, I would do the review and merge in a few days. Thanks.
