-
Notifications
You must be signed in to change notification settings - Fork 214
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
Deprecate @service
version and allow @OpenAPI.info
to take all properties allowed by openapi
#2902
Deprecate @service
version and allow @OpenAPI.info
to take all properties allowed by openapi
#2902
Conversation
@service
version and allow @OpenAPI.info
to take all properties allowed by openapi
All changed packages have been documented. |
You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/2902/ Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/2902/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically, the info block allows arbitrary extensions (prefixed with x-
), but I suspect these are not commonly used. If we need to support them, presumably we can add another optional parameter.
…operties allowed by openapi (microsoft#2902) fix [microsoft#2821](microsoft#2821) ## Deprecate `@service({version` Using this property will emit a deprecation warning ## Cover everything with `@OpenAPI.info` Makes sure all the properties allowed on the `info` object of openapi specification can also be provided in `@info`. The properties will either override other ways of specifying those previously or be the only way. - `@info({description` would override `@doc` on service namespace - `@info({summary` would override `@summary` on service namespace - `@info({title` would override `@service({title}` on service namespace
fix #2821
Deprecate
@service({version
Using this property will emit a deprecation warning
Cover everything with
@OpenAPI.info
Makes sure all the properties allowed on the
info
object of openapi specification can also be provided in@info
. The properties will either override other ways of specifying those previously or be the only way.@info({description
would override@doc
on service namespace@info({summary
would override@summary
on service namespace@info({title
would override@service({title}
on service namespace