fix!: typing issues with some input fields #1199
Closed
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
MartinWeb
previously approved these changes
Sep 3, 2024
The package used to build the types with @types/react v17 and using it in a v18 project causes a flood of warning issues. For example, onPointerLeaveCapture was required by the typing as poped as an issue in the build logs BREAKING CHANGE: dropped support for react 17 and 16
JLou
force-pushed
the
fix/type-warnings
branch
from
ca39128 to
66b39d1
Compare
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.
The package used to build the types with @types/react v17 and using it in a v18 project causes a flood of warning issues. For example, onPointerLeaveCapture was required by the typing as poped as an issue in the build logs
BREAKING CHANGE: dropped support for react 17 and 16