refactor: enforce strict types in test case mapping #1085
Merged
+556
−559
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Belco90
approved these changes
Sep 18, 2025
|
🎉 This PR is included in version 7.8.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checks
Changes
mapandflatMapcalls used in test case definitionsMotivation
This change improves developer experience and code maintainability by leveraging TypeScript's type system more effectively in test definitions. With proper type arguments, we gain better autocompletion, stricter checks, and clearer code when working with test case arrays.
Context
Since the diff is expected to be large, this PR updates only the tests for the rule mentioned in issue #202 for now.