-
Notifications
You must be signed in to change notification settings - Fork 61
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 code-test
CLI
#81
Comments
This would be a super useful feature. |
5 tasks
remcohaszing
added a commit
to remcohaszing/vscode-test
that referenced
this issue
Aug 26, 2022
`parseArgs` is used as a command line argument parser, because it polyfills an experimental Node.js API. Eventually this means this dependency can be removed. `@types/node` was updated to version 18 in order to provide types for `@pkgjs/parseargs`. Closes microsoft#81
remcohaszing
added a commit
to remcohaszing/vscode-test
that referenced
this issue
Aug 26, 2022
`parseArgs` is used as a command line argument parser, because it polyfills an experimental Node.js API. Eventually this means this dependency can be removed. `@types/node` was updated to version 18 in order to provide types for `@pkgjs/parseargs`. Closes microsoft#81
Closed
Is there anything blocking this? My PR has been ready for about a year, but isn’t getting any attention. |
This is now done, docs are here: https://github.com/microsoft/vscode-docs/blob/vnext/api/working-with-extensions/testing-extension.md#quick-setup-the-test-cli |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now we require a
runTests
script. However we could serve 99% of users with a CLI instead, which would be easier to invoke and more friendly with argument passing.The text was updated successfully, but these errors were encountered: