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
feat(yargs): add types for yargs@v17 #52169
Conversation
@bcoe Thank you for submitting this PR! I see this is your first time submitting to DefinitelyTyped 👋 — I'm the local bot who will help you through the process of getting things through. This is a live comment which I will keep updated. 1 package in this PR
@bcoe: I see that you have added yourself as an owner, are you sure you want to become an owner? Code ReviewsBecause this is a widely-used package, a DT maintainer will need to review it before it can be merged. Status
Once every item on this list is checked, I'll ask you for permission to merge and publish the changes. Diagnostic Information: What the bot saw about this PR{
"type": "info",
"now": "-",
"pr_number": 52169,
"author": "bcoe",
"headCommitOid": "291405ff143eb82ec9e3f1e11176f349a75c716c",
"lastPushDate": "2021-05-21T00:33:35.000Z",
"lastActivityDate": "2021-05-21T00:33:35.000Z",
"hasMergeConflict": false,
"isFirstContribution": true,
"tooManyFiles": false,
"popularityLevel": "Critical",
"pkgInfo": [
{
"name": "yargs",
"kind": "edit",
"files": [
{
"path": "types/yargs/index.d.ts",
"kind": "definition"
},
{
"path": "types/yargs/v16/helpers.d.ts",
"kind": "definition"
},
{
"path": "types/yargs/v16/index.d.ts",
"kind": "definition"
},
{
"path": "types/yargs/v16/tsconfig.json",
"kind": "package-meta-ok"
},
{
"path": "types/yargs/v16/tslint.json",
"kind": "package-meta",
"suspect": "not [the expected form](https://github.com/DefinitelyTyped/DefinitelyTyped#user-content-linter-tslintjson) (check: `rules`)"
},
{
"path": "types/yargs/v16/yargs-tests.ts",
"kind": "test"
},
{
"path": "types/yargs/v16/yargs.d.ts",
"kind": "definition"
},
{
"path": "types/yargs/yargs-tests.ts",
"kind": "test"
}
],
"owners": [
"poelstra",
"mizunashi-mana",
"pushplay",
"JimiC",
"steffenvv",
"forivall",
"ExE-Boss",
"Aankhen"
],
"addedOwners": [
"bcoe"
],
"deletedOwners": [],
"popularityLevel": "Critical"
}
],
"reviews": [],
"ciResult": "pass"
} |
🔔 @poelstra @mizunashi-mana @pushplay @JimiC @steffenvv @forivall @ExE-Boss @Aankhen — please review this PR in the next few days. Be sure to explicitly select |
@bcoe Unfortunately, this pull request currently has a merge conflict 😥. Please update your PR branch to be up-to-date with respect to master. Have a nice day! |
@bcoe The CI build failed! Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
@bcoe The CI build failed! Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings. Let’s review the numbers, shall we? These typings are for a version of yargs that doesn’t yet exist on master, so I’ve compared them with v16.0. Comparison details 📊
It looks like nothing changed too much. I won’t post performance data again unless it gets worse. |
Introduces parseSync/parseAsync, allowing an application to explicitly state whether or not it expects the parse goal of yargs to be asynchronous or synchronous. Refs: DefinitelyTyped/DefinitelyTyped#52169
this issue is tracking the additional work to be done for yargs@v17. |
Re-ping @poelstra, @mizunashi-mana, @pushplay, @JimiC, @steffenvv, @forivall, @ExE-Boss, @Aankhen: This PR has been out for over a week, yet I haven't seen any reviews. Could someone please give it some attention? Thanks! |
Please mark the PR as "Draft" status in github so that wee ol' typescript-bot knows it's still WIP! |
@forivall just released |
Re-ping @poelstra, @mizunashi-mana, @pushplay, @JimiC, @steffenvv, @forivall, @ExE-Boss, @Aankhen: This PR has been out for over a week, yet I haven't seen any reviews. Could someone please give it some attention? Thanks! |
@bcoe Unfortunately, this pull request currently has a merge conflict 😥. Please update your PR branch to be up-to-date with respect to master. Have a nice day! |
It has been more than two weeks and this PR still has no reviews. I'll bump it to the DT maintainer queue. Thank you for your patience, @bcoe. (Ping @poelstra, @mizunashi-mana, @pushplay, @JimiC, @steffenvv, @forivall, @ExE-Boss, @Aankhen.) |
I just published |
I just published |
yargs@17 is a major overhaul of how asynchronous commands, builders, and middleware are handled (it's now possible to
await parse()
andawait .argv
).This should not be merged until yargs/yargs#1876 is released (once Node 10 is EOL).
npm test <package to test>
.If changing an existing definition: