Documentation: fix linter errors with TypeScript declarations in Vitest setup instructions #696
Conversation
This file contains 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
ESLint gives a `no-undef` error without the `<T = any>` constraint in the type definition. This PR adds the constraint to help prevent people from getting linting errors from the configuration.
|
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.
ESLint (with the
typescript-eslintplugin) gives ano-undeferror without the<T = any>constraint in the type definitions. This PR adds the constraint to help prevent people from getting linting errors from the configuration. TypeScript doesn't seem to be fussed either way, but this should save people a minor annoyance.What
Add type variable to TypeScript + Vitest setup instructions in the documentation.
Why
Prevent minor annoyances when linting fails for people who use the definitions.