We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I noticed when switching yargs to use gts for linting, that variables inside an interface are flagged as unused by no-unused-vars:
no-unused-vars
export interface YargsInstance { $0: string; argv: Arguments; customScriptName: boolean; parsed: DetailedArguments | false; // The methods below are called after the parse in yargs-parser is complete // and perform cleanup on the object generated: _postProcess<T extends Arguments | Promise<Arguments>>( argv: T, populateDoubleDash: boolean, calledFromCommand?: boolean ): T; _copyDoubleDash<T extends Arguments>(argv: T): T; _parsePositionalNumbers<T extends Arguments>(argv: T): T;
Will lead to warnings like:
1748:5 warning 'populateDoubleDash' is defined but never used @typescript-eslint/no-unused-vars
The actual definition of self._postProcess does have the populateDoubleDash variable, and uses it.
self._postProcess
populateDoubleDash
Refs: yargs/yargs#1777
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I noticed when switching yargs to use gts for linting, that variables inside an interface are flagged as unused by
no-unused-vars
:Will lead to warnings like:
The actual definition of
self._postProcess
does have thepopulateDoubleDash
variable, and uses it.Refs: yargs/yargs#1777
The text was updated successfully, but these errors were encountered: