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 deprecated
version argument to the @Available
directive
#441
Comments
I would argue that we shouldn't add
|
isBeta
and isDeprecated
in the @Available
directivedeprecated
version argument to the @Available
directive
Adding a new argument to an existing directive is a pretty good first task for someone who wants to learn about how directives work in DocC. There are existing tests for this type that can be updated to cover combinations of both arguments. |
Hey, I am wondering if this is still open! I would love to pick it up and add the new directive into DocC. |
@mustiikhalil yes, AFAIK this is still open and no-one has started working on it yet. That said, might be worth double checking with @sofiaromorales who is working on some other availability improvements. |
That's perfect, I can pick it up after input from @sofiaromorales incase it's still needed. |
@mustiikhalil, sure, feel free to take on this issue 🙂 |
So I started working on it here #851 and from what I can see, I've implemented all the required fields for it to work as expected, however I wonder if I missed something. |
Feature Name
Specify deprecated version in
@Available
directiveDescription
The initial implementation of
@Available
(#440) only supports specifying the "introduced" version. We should add support for specifying a "deprecated" version as well.Motivation
No response
Importance
No response
Alternatives Considered
No response
The text was updated successfully, but these errors were encountered: