Thanks to visit codestin.com
Credit goes to github.com

Skip to content

test: fix vscode launch configuration for windows #1523

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

Merged
merged 5 commits into from
Jan 26, 2020
Merged

test: fix vscode launch configuration for windows #1523

merged 5 commits into from
Jan 26, 2020

Conversation

armano2
Copy link
Collaborator

@armano2 armano2 commented Jan 25, 2020

fixes #1519

@armano2 armano2 added the tests anything to do with testing label Jan 25, 2020
@armano2 armano2 self-assigned this Jan 25, 2020
@typescript-eslint

This comment has been minimized.

@codecov
Copy link

codecov bot commented Jan 26, 2020

Codecov Report

Merging #1523 into master will not change coverage.
The diff coverage is 96.87%.

@@           Coverage Diff           @@
##           master    #1523   +/-   ##
=======================================
  Coverage   95.49%   95.49%           
=======================================
  Files         150      150           
  Lines        6639     6639           
  Branches     1880     1880           
=======================================
  Hits         6340     6340           
  Misses        112      112           
  Partials      187      187
Impacted Files Coverage Δ
...-plugin/src/rules/explicit-function-return-type.ts 100% <100%> (ø) ⬆️
.../eslint-plugin/src/util/explicitReturnTypeUtils.ts 100% <100%> (ø) ⬆️
packages/eslint-plugin/src/util/astUtils.ts 84.37% <80%> (ø) ⬆️
...plugin/src/rules/explicit-module-boundary-types.ts 85.45% <94.44%> (ø) ⬆️

"--runInBand",
"--no-cache",
"--no-coverage",
"${fileBasename}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be fileBasenameNoExtension
fileBasename will include .ts, which means you can only run the test if you open the test file (because semi.ts won't match semi.test.ts)

Suggested change
"${fileBasename}"
"${fileBasenameNoExtension}"

"--runInBand",
"--no-cache",
"--no-coverage",
"${fileBasename}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"${fileBasename}"
"${fileBasenameNoExtension}"

@bradzacher bradzacher merged commit 03221d2 into typescript-eslint:master Jan 26, 2020
@JoshuaKGoldberg
Copy link
Member

Thank you!

@armano2 armano2 deleted the vscode-launch branch January 27, 2020 00:21
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tests anything to do with testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Jest Test Current eslint-plugin Rule" does not trigger on Windows
3 participants