--make-paths-enum is missing

[Inrixia]

After updating from 5.4.1 to 6.x.x the argument --make-paths-enum is no longer working.

As far as I can tell there is no way to get this functionality since the last update? This completely breaks this library for me making it unusable as I need path's as variables that I can actually use.

Is there a reason why this was removed or a way to enable it in the newer version?

[drwpow]

Correct. Explanation here as to why it was removed: https://github.com/drwpow/openapi-typescript/releases/tag/v6.0.0

[laurenz-glueck]

@drwpow I just came across this change which makes it pretty hard to update to v6 if you dependent on the ApiPaths enum in you application.
Is there any workaround?
Or are you planning to bring this back at some point?

[laurenz-glueck]

@drwpow Just wanted to ask again as I didn't got a response on my previous comment...
Are there any plans to bring back the generation of the ApiPaths enum?

[laurenz-glueck]

@drwpow I took a closer look at the code and I think I understood why the option was removed...
If I understand the transformers concept correct, then the problem is that the paths are already used for the transformPathsObject transformer right?

Nevertheless, I think it's important for some users to get the ApiPaths enum.

That's why I have created a draft PR that brings back the generation of the ApiPaths enum:
#2052

The PR is definitely just a draft and probably needs some improvements...
But maybe you could take a look at it and give me your feedback?

[drwpow]

@laurenz-glueck Thanks for being persistent with this! I apologize—this just kept slipping through the cracks and I wasn’t intentionally ignoring this conversation. Appreciate you pushing this forward. The simplest answer was it was just beyond my ability to maintain originally, and I appreciate you making the contributions and keeping the conversations going to make it happen 🙂

In a somewhat-related update, in the past few months we’ve gone from this project being maintained by only me, to having 4 dedicated maintainers, to prevent these sorts of things from slipping through the cracks again. What that means isn’t that every feature will be added, but we’ll at the very least be better at responding to all the conversations and making thinking/project direction clearer.