-
Notifications
You must be signed in to change notification settings - Fork 45
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
Show value in Webstorm doesn't work #2530
Comments
It looks like you are setting Try removing these lines from your Wallaby config: - "files": [
- {
- "pattern": "src/**/*.js",
- "instrument": false,
- "load": true
- },
- "!./src/**/__tests__/**/*.spec.js"
- ],
- "tests": [
- "./src/**/__tests__/**/*.spec.js"
- ] Also, the number of files in your repo that is tracked by Wallaby |
Unfortunately, it does not help me. I did as you said, and still, It does not work. |
Is there a specific reason for the overrides? Does Wallaby work without them? Your jest configuration also shows that you are excluding a number of files from being included from code-coverage which may also explain why your coverage is not working. Please also try removing these patterns to see if that fixes your problem:
|
If set conf.type = automatic in Webstorm, everything is fine. But if I create custom config file
it does not work. I need custom config to rewrite some jest.config rules, for example |
Can you please share the code of your custom config? In your code sample, the Also, when you say
Why do you need a custom config for it and can not set the same in you main Jest config? |
|
Thanks. If you delete const fs = require('fs');
const config = require('./jest.config');
module.exports = {
...config,
- watchPathIgnorePatterns: [
- ...fs.readdirSync('./').filter((path) => path !== 'src'),
- 'src/actions',
- 'src/styles',
- 'src/tests',
- 'src/plugins',
- 'src/components',
- ],
}; and restart Wallaby, does it start working? Also just to confirm:
This does improve Jest's CLI performance a bit as well, not just Wallaby's. |
I have a monorepo project:
And right now my jest config in folder |
@i-have-no-name - we'll need to know about your file paths, see latest Wallaby diagnostics, etc. to diagnose further. Could you please provide us with a sample repo with a similar project/jest configuration that also has your problem? |
|
Unfortunately we can't reproduce the issue. We have created this sample repo /~https://github.com/ArtemGovorov/wallaby-2530 with your folder structure, and starting exclusive test run correctly works for us: Can you please clone the repo, |
Your example works. |
Thanks for checking and investigating what setting was causing the issue. The bug is fixed and the fix has been published in the latest core version 1.0.971 (you may just restart your IDE and then start wallaby.js to force the core update immediately). |
Issue description or question
Hi. I have jest.config and overrides some rules in package.json
When I run "Add to exclusive Test run" on my test file and try to "Show value" in my source file It doesn't show any values in "Explorer"
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: