fix: add support for exactOptionalPropertyTypes
in type definitions
#391
+25
−2
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.
Prerequisites checklist
What is the purpose of this pull request?
When using
@eslint/markdown
as a plugin in an ESLint config file, TypeScript throws the following error if theexactOptionalPropertyTypes
compiler option is enabled:For example, this can be triggered by using
plugins: { markdown }
in:This PR fixes the issue.
What changes did you make? (Give an overview)
I noticed that the
Plugin
type was unused, so I updated it to be compatible withexactOptionalPropertyTypes
and began using it, without breaking existing tests.Related Issues
-
Is there anything you'd like reviewers to focus on?
-