test.concurrent support
See original GitHub issueit appears that the linter ignores test.concurrent
calls, for example - currently I have the jest/no-empty-title
rule enabled:
with just test
:
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@daniellacosse from memory, a couple of things need doing:
concurrent
needs to be added as a value in the right enum,concurrent
should be checked for what it supports, as while I suspect it is onlytest.concurrent
, we need to know ifit.concurrent
,test.concurrent.only
,test.concurrent.each
, etc are valid in jest.jest/no-empty-title
isn’t the only one that this affects (or maybe it is - either way, need to check).jest/no-empty-title
rule needs to be updated to includeconcurrent
in what it checks. iirc this could be just a matter of adding it to the right enum, but otherwise it’ll just be a matter of passing the new enum value in the right place.Go for it!