-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
add language metadata into "info" object #70
Comments
Updating vendorExtension description to new pattern
We haven't included that in Swagger 2.0. I'm closing this issue for now but marking it as a proposal for the next version of the spec. If more people request it, we may include it. |
Parent: #560. |
This request comes form use of Swagger within European Projects whre cross country API usage is fostered. |
But is the content language actually static enough to be described in the swagger definition? Isn't this more of a runtime property? (Like what would be in the |
Usually yes I tipically have an API that return data from a DB and on the majority of the cases the text inside is in a single language. |
It could be useful to have a language element in the info object to represent the language used in the API data: it could be expressed using classical IT, ES, etc codes this way it can be used to translate or deal with the content of the API
The text was updated successfully, but these errors were encountered: