openapi-code-generator

A code generation tool for openapi 3 / 3.1 specifications written in typescript, primarily aimed at generating typescript clients and server stubs. Other target languages may be added in future. (by mnahkies)

Openapi-code-generator Alternatives

Similar projects and alternatives to openapi-code-generator

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better openapi-code-generator alternative or higher similarity.

openapi-code-generator reviews and mentions

Posts with mentions or reviews of openapi-code-generator. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-29.
  • TypeSpec: A New Language for API-Centric Development
    11 projects | news.ycombinator.com | 29 Apr 2024
    Whilst it's not as expressive/flexible as typespec, and in my experience it's not always well supported by tooling, you can do $ref's across files in openapi specifications.

    Eg: https://github.com/mnahkies/openapi-code-generator/blob/main...

  • Show HN: Pre-alpha tool for analyzing spdx SBOMs generated by GitHub
    3 projects | news.ycombinator.com | 21 Apr 2024
    I've become interested in SBOM recently, and found there were great tools like https://dependencytrack.org/ for CycloneDX SBOMs, but all I have is SPDX SBOMs generated by GitHub.

    I decided to have a go at writing my own dependency track esque tool aiming to integrate with the APIs GitHub provides.

    It's pretty limited in functionality so far, but can give a high level summary of the types of licenses your repository dependencies use, and let you drill down into potentially problematic ones.

    Written in NextJS + mui + sqlite, and using another project of mine to generate most of the API boilerplate/glue (https://github.com/mnahkies/openapi-code-generator)

  • Show HN: Konfig – SDKs for APIs to write and maintain less API integration
    2 projects | news.ycombinator.com | 3 Apr 2024
    Congratulations on launching, you have some interesting ideas in there.

    Using a LLM to generate missing operation ids isn't something I've tried, instead I simply combine http method plus path segments which at least guarantees uniqueness [1]. I do a similar thing for extracting and naming inline schemas based on the operation and media types [2].

    How do you prevent naming collisions? And do you find the resulting names to be significantly better than a deterministic approached like I described?

    I'll definitely checkout the curated specifications - always useful to get more high quality (and hopefully varied) specifications to test my code generator with, and the lint rules is a great idea - I've had to explain what patterns lend themselves well to code generation many times.

    I'm on mobile so may have missed it, but looking at one of your typescript examples I couldn't see any runtime response body validation, is this something you're thinking about?

    - [1] https://github.com/mnahkies/openapi-code-generator/blob/main...

  • Write OpenAPI with TypeSpec
    7 projects | news.ycombinator.com | 27 Mar 2024
    Yeah I'm also on the schema first side of the debate.

    I think for me it comes down to a few key points:

    - APIs are forever, the choice of language/framework is an implementation detail

    - Constraining yourself to what can be represented in the specification is better than generating a specification from implementation that may not be capable of expressing the full details

    - When working with diverse languages it provides a common ground/language for discussing API changes. Eg: if you have java backend, kotlin android, swift iOS, react/whatever web you can bring everyone together with the spec

    - Subjective, but a good spec will include a bunch of documentation and examples that tend to create a lot of noise in the code. I personally prefer to keep this in the spec and the implementation smaller

    I think the main counterpoint to this is that you can generate the spec and then take that and change your mind if you later change language/framework etc - it's not a one-way door.

    My biggest bug bear is that regardless of spec first or implementation first, you should have something you write once and generate the rest of the glue from (eg: docs, client sdks). Writing each piece manually/independently always leads to drift and bugs.

    (I'm working on my own little openapi -> typescript code generator over here https://github.com/mnahkies/openapi-code-generator - eventually plan to support more than typescript, and adding typespec support is something I'm currently considering)

  • A note from our sponsor - SurveyJS
    surveyjs.io | 4 May 2024
    With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more →

Stats

Basic openapi-code-generator repo stats
5
12
8.8
4 days ago

mnahkies/openapi-code-generator is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of openapi-code-generator is TypeScript.


Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com