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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update types and props for compatibility with React 18 #7150
Update types and props for compatibility with React 18 #7150
Changes from 13 commits
77bf286
713b2ec
c72409c
e47d9f6
67a68f9
8234337
c638cbe
bc14833
e1b374c
c9aa576
074b795
5508c77
0c815e9
f503549
fd385b9
21a62fc
b086803
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we're expecting children to be
React.ReactElement<HotkeyProps>
. Should we use that type overobject
?blueprint/packages/core/src/components/hotkeys/hotkeys.tsx
Line 57 in 0c815e9
Or was the goal to preserve the same type definition of
HotkeyProps
and avoid compile breaks on consumers?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is a nitpick, but I've personally been avoiding
React.PropsWithChildren<...>
since I see the React docs usually write thechildren
prop directly.https://react.dev/learn/typescript#typing-children
Having the
children
prop directly in the interface also makes it easier to add a JSDoc on the field.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fd385b9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: Similar comment around potentially writing the
children
field directly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
21a62fc