Mark api/operations as obsolete/deprecated
Our api is updating frequently. Some operations and even whole api could be deprecated.
We can't mark api/operations as deprecated. Now, only modify description could help us but it's not enough. Because nobody really read the description from start to end. And we can't highlight information in it.
Please- give as a button "Mark api/operation as deprecated" + textbox for description why it happened and what other method should be used now(maybe with checking that new operations is available).
Also highlight information about api/operation is deprecated in a description or somewhere else for a current consumers.
And in the final- please make api/operation hidden for all new consumers by default.
Sychev Igor
shared this idea
Thanks for your feedback.
4 comments
-
Anonymous
commented
Kinda disappointing after nearly 5 years this still isn't supported. OpenAPI deprecation flags (as well as lots of other missing OpenAPI features) should be supported
-
Geringer, Keith
commented
This feature should be supported via the OpenAPI document.
-
John Christopher Knutsen Kruiderink
commented
This feature was added to Open API 3.0(https://swagger.io/docs/specification/paths-and-operations/).
However, marking operations as deprecated in the Open API document does not effect documentation in the developer portal. -
SP
commented
Do we have any update on this topic - "Mark api/operations as obsolete/deprecated"?