3 ms·
> Our goal is to remove the need to develop custom client SDKs for an REST API. Aren't there enough tools already for OpenAPI to do this?
by manojlds 4y ago
> Our goal is to remove the need to develop custom client SDKs for an REST API.
Aren't there enough tools already for OpenAPI to do this?
- pixelrevision 4y agoYes. And the tooling is pretty straightforward to plug into generally if you need to tweak things. I’ve found that the biggest barrier here is generally not in openapi tooling, but in getting people to take time out to leverage it. This is one of those places that having lots of options and alternatives typically makes things worse.
- throwawaymaths 4y agoto be fair a lot of them are absolutely terrible. The top .NET one seems to be maintained by very unprofessional amateurs, has ~> 1000 open issues, some open for years, and definitely doesn't do multipart encoding correctly. Not that problem would be solved by having yet another spec.
- klysm 4y agoYeah the .NET ecosystem around openapi is horrible. I at least want the typescript client story to be good
- solarkraft 4y ago> Yeah the .NET ecosystem (...) is horrible :-) That's how it felt when I was developing for it. But that's because I was interested in cool new things, not decade-old, establish enterprise stuff. I suppose it has changed a bit in recent years, but it still doesn't exactly follow trends very enthusiastically. Which can be a good thing. But also means tooling around legitimately useful new things can be quite lacking.
- klysm 4y agoI wouldn’t consider REST API tech to be very trendy, it’s kind of old wave and I would expect a good story for it.
- manojlds 4y agoThis one doesn't even mention .NET in the generators.