Skip to content
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

Should deprecate/deprecated be included in the docs and types? #1760

Closed
natasha-audrey opened this issue Sep 18, 2020 · 1 comment · Fixed by #1762
Closed

Should deprecate/deprecated be included in the docs and types? #1760

natasha-audrey opened this issue Sep 18, 2020 · 1 comment · Fixed by #1762
Labels

Comments

@natasha-audrey
Copy link
Contributor

yargs/yargs.js

Line 636 in 8aae333

const deprecate = opt.deprecate || opt.deprecated

I see this was added in #1559 (added in v15.2.0) - but I don't see it listed in the docs in option's documentation or in @types/yargs@15.0.5.

It would be nice to use in my typescript project without a @ts-ignore


Relevant issue: #1518

@bcoe bcoe added the docs label Sep 19, 2020
@bcoe
Copy link
Member

bcoe commented Sep 20, 2020

@NathanYocum we've opted to not ship types for yargs, so to add this to the type definition I suggest creating an issue on the @types/yargs definition in definitely typed.

I agree we should definitely document this feature in the API, if it hasn't been 😄

I would happily take a patch for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants