This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
Mark API as deprecated #399
Labels
Comments
|
This is very very important feature we all need for APIs. |
|
+1 |
|
It will be very good feature, that make API documentation more transparent. How often apiary developers implements proposals? :-) |
|
not implement yet? |
|
Is there a roadmap for implementing the |
|
In 2021 , 5 years later I am finding same feature😂 |
tobice
added a commit
to apify/apify-docs
that referenced
this issue
Feb 13, 2024
Runs and builds have had dedicated namespaces for a long time (/actor-runs/:run_id and /actor-builds/:build_id). The API reference wasn't making it very clear, so this is an attempt to improve the situation. Unfortunately, there is no native way for API Blueprint to mark endpoints as deprecated [1], so good old bold text will have to do. [1] apiaryio/api-blueprint#399
tobice
added a commit
to apify/apify-docs
that referenced
this issue
Feb 14, 2024
…ted (#859) Runs and builds have had dedicated namespaces for a long time (/actor-runs/:run_id and /actor-builds/:build_id). The API reference wasn't making it very clear, so this is an attempt to improve the situation. Unfortunately, there is no native way for API Blueprint to mark endpoints as deprecated [1], so good old bold text will have to do (advice from ChatGPT). [1] apiaryio/api-blueprint#399
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There should be a property to indicate whether a API is deprecated
The text was updated successfully, but these errors were encountered: