Comments (5)
This should be a different rule that handles this kind of behavior. Open for PRs
from eslint-plugin-vitest.
Should there be an option to enforce this only for concurrent
, but allow it to be forced for everything?
Note: I’m new to Vitest. From my reading of the docs, I though the destructured form was only “needed” in the concurrent case.
from eslint-plugin-vitest.
Yeah, destructuring is needed for concurrent
tests. Wouldn't this be great if it was a different rule?
from eslint-plugin-vitest.
Yes, I think it should be a new rule.
- I think it would be included in the
recommended
set to require it forconcurrent
cases. - Assuming you can destructure in the non-concurrent case (I'm new to Vitest), I think we should have an option similar to
always
that enforces it everywhere. (This would make it easier to switch to concurrent.) - Ideally, this would be auto-fixable.
I have never written an ESLint rule, so I do not know how “involved” this would be to submit a PR, but it could be good learning.
from eslint-plugin-vitest.
this was resolved check docs
from eslint-plugin-vitest.
Related Issues (20)
- Feature request: formatting rules HOT 1
- Invalid flat config HOT 2
- `bench` throw error `Prefer using it instead of test within describe`
- `expect-expect` fails even if `expectTypeOf` is present HOT 7
- Add require `describe`, `it` and `vi` import HOT 1
- Extend the `no-identical-title` rule to support `suite` test block pattern HOT 4
- Consider rule for naming mocks created with `vi.fn()` HOT 1
- Results of weekly scheduled smoke test HOT 1
- Throwing with ESLint 9 and flat config HOT 1
- [BUG] Converting circular structure to JSON HOT 5
- Please provide non-flat config HOT 6
- Declaration file missing plugin configs
- Results of weekly scheduled smoke test HOT 8
- TypeError: Converting circular structure to JSON when extend the recommended HOT 3
- Feature request: `prefer-vi-mocked` HOT 1
- tsc: Fix issues related to types HOT 1
- Readme docs is outdates
- Publish v0.6.0 to NPM HOT 19
- pnpm complains of unmet peer dependency. HOT 6
- `vitest/unbound-method` does not work in legacy config HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eslint-plugin-vitest.