-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark preferred version of API #219
Comments
Hmm... I guess we could do this, but I'm not sure we should think about versions this way. All versions that are not preview should be equally good for customers to consume. There is no preference other than feature set. We could provide guidance to point toward the latest, or simply have the convention rather than having to keep updating the symlink when a new version is available. |
Yes, but imagine person see your API for the first time without any previous experience with it. I working on catalog of OpenAPI specs for public APIs.
Alternative you can mark it inside spec itself. |
* drastically simplified the subscription creation by removing the concept of billing context and changing offer to an enum * responded to review feedback * fixed spelling errors
The API documented inside the Stable folder version are the ones that customer would write stable code on, "Preffered" would be a bit subjective depending on what the customers are looking for. Some prefer latest stable other prefer to lock on a specific version. Ofcourse the more recent version that you adopt the more goodness of features you get :) Thanks Closing and please re-open if you have other questions Thanks Samer |
Some APIs have multiple swagger files documenting different versions.
In my service, by default show preferred version of API.
Could you please mark preferred version somehow?
For example, Git support symlinks, so you can make
$api/preferred/
point to dir with preferred version.The text was updated successfully, but these errors were encountered: