Suggestion
Some RuleTester tests in this repo are generated dynamically. Auto-generating tests like that can help create comprehensive test coverage for rules - but:
- They tended to exponentially grow in size as more cases get grown
- They make it hard to see what cases are or aren't being tested
- They're not very statically analyzable
We'd like to move away from these auto-generated / dynamic test cases. That specifically means making all test cases passed to RuleTester be completely inline plain old JavaScript objects. No .flatMaps/.maps, no dedupeTestCases, helper functions, etc.
This issue tracks doing so for packages/eslint-plugin/tests/rules/return-await.test.ts.
Additional Info
💖
Suggestion
Some
RuleTestertests in this repo are generated dynamically. Auto-generating tests like that can help create comprehensive test coverage for rules - but:We'd like to move away from these auto-generated / dynamic test cases. That specifically means making all test cases passed to
RuleTesterbe completely inline plain old JavaScript objects. No.flatMaps/.maps, nodedupeTestCases, helper functions, etc.This issue tracks doing so for
packages/eslint-plugin/tests/rules/return-await.test.ts.Additional Info
💖