search

apigee-127 / swagger-tools

A Node.js and browser module that provides tooling around Swagger.
MIT License
701 stars 373 forks source link

This project, or swagger-node? #564

Open jwalton opened 6 years ago

jwalton commented 6 years ago

Not sure if an issue is the best place to ask this, but:

I'm looking to incorporate swagger into an existing project, and I'm totally new to swagger. Should I be using swagger-tools or swagger-node as a starting point? I see some shared dependencies between the two. Are these projects related in some way?

swagger-node is linked from swagger.io, which I would think would be a point in it's favor. But I notice swagger-node and friends haven't seen many commits in the past two years, and the "swagger" cli tool produces an express framework using an ancient version of swagger-connect. It seems very opinionated in terms of where I install config files and how my project should be laid out (which I'm not so fond of, as I'm adding this to an existing project).

Any advice for a swagger newbie? :)

jcferrer commented 6 years ago

I have been using the a127 framework since 2015, which is the predecesor in a way of the swagger-node project. The a127 project uses swagger-tools and other libraries that nicely complement the API building experience. To be honest, I have been very successful running apps using this framework in real production environments.

I've been wanting to migrate my apps to the swagger-node project for some time, but some of the functionality I get from a127 is missing. I share the same concern about the lack of activity in the swagger-node project and also the fact that swagger-tools is deprecated in favor of sway.

Since you are just starting, swagger-node is a straight forward approach. I really recommend it. I have looked at other frameworks but none of them seem to be as clean.

JC