Deprecate @service({version}
#2821
Assignees
Labels
breaking-change
A change that might cause specs or code to break
deprecation
A previously supported feature will now report a warning and eventually be removed
triaged:core
Milestone
Comments
timotheeguerin
added
breaking-change
|
est: 5 |
timotheeguerin
added a commit
that referenced
this issue
Feb 28, 2024
…operties allowed by openapi (#2902) fix [#2821](#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
markcowl
pushed a commit
to markcowl/cadl
that referenced
this issue
Mar 8, 2024
…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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
from design #2812
@service({version}, cleanup docs to remove reference@OpenAPI.infoto allowtitleandversion(Somehow works already@OpenAPI.info({version})(or general don't use openapi library)The text was updated successfully, but these errors were encountered: