typecheck settings is not respected
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- devtools, testing-qa
Research direction
Start by reproducing the issue in the linked express-typed commit and in the Vitest typecheck example, comparing npx vitest with running tests from the IDE extension. Inspect the extension's test execution and typecheck handling, especially how *.test-d.ts files are treated. Done means type errors in type-only test files are reported when tests run from the extension.
Written by the indexing model from the issue text.
Description
Describe the bug
typecheck settings is not respected
in the gif you can see:
- running
npx vitestcorrectly check typing. - running the test from the IDE extension does not catch type error, even though this file only checks for typing only
- this extension should respect filed
*.test-d.tsfor type tests only tests.
Reproduction
first of all, awesome extension!
to reproduce:
git clone https://github.com/Eliav2/express-typed
// or, checkout exact commit (in case the repo would be changed)
git clone --bare https://github.com/Eliav2/express-typed.git
cd express-typed.git
git checkout 6aec67bfe1c849edfac0a85d41a1df0faa60cb0d
now run npx vitest at root directory, or run tests from the IDE.
OR small example
from vitest docs - Play Online
This extension would not correctly catch type.test-d.ts type errors.
Output
.
Version
v0.8.6
Validations
- Check that you are using the latest version of the extension
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
- Dominant language
- TypeScript
- Stars
- 924
- Forks
- 122
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 6
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vitest-dev/vscode
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
vitest-dev/vscode#776 · 1 reaction ·
-
pending triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
vitest-dev/vscode#825 · 1 comment · 7 reactions ·
-
pending triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
vitest-dev/vscode#824 · 5 comments · 19 reactions ·
-
p3-minor-bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
vitest-dev/vscode#823 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
vitest-dev/vscode#822 ·
All issues in vitest-dev/vscode
Similar issues
-
bug(cli): hapi doctor inline-media prints a fabricated B:\ helper-script path in packaged installs Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Crush Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
catppuccin/catppuccin#3125 ·
-
Add a SECURITY.md Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ElementsProject/cln-application#167 · 1 comment · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Quantco/pnpm-licenses#17 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100