-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
fix: Incorrect onToggle event type #4615
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -351,6 +351,10 @@ const acceptsStringAsLength = <div style={{ marginTop: '20px' }} />; | |
|
||
const ReturnNull: FunctionalComponent = () => null; | ||
|
||
// Should accept arbitrary properties outside of JSX.HTMLAttributes | ||
h('option', { x: 'foo' }); | ||
createElement('option', { value: 'foo' }); | ||
|
||
// Refs should work on elements | ||
const ref = createRef<HTMLDivElement>(); | ||
createElement('div', { ref: ref }, 'hi'); | ||
|
@@ -375,13 +379,17 @@ const onBeforeInput = (e: h.JSX.TargetedInputEvent<HTMLInputElement>) => {}; | |
createElement('input', { onBeforeInput: onBeforeInput }); | ||
h('input', { onBeforeInput: onBeforeInput }); | ||
|
||
// Should accept onSubmit | ||
const onSubmit = (e: h.JSX.TargetedSubmitEvent<HTMLFormElement>) => {}; | ||
<form onSubmit={e => e.currentTarget.elements} />; | ||
createElement('form', { onSubmit: onSubmit }); | ||
h('form', { onSubmit: onSubmit }); | ||
|
||
h('option', { value: 'foo' }); | ||
createElement('option', { value: 'foo' }); | ||
Comment on lines
-383
to
-384
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry for the diff, placed this rather wonkily a few weeks ago. Moved it out so it wasn't sat in the middle of the event tests. |
||
// Should accept onToggle | ||
const onToggle = (e: h.JSX.TargetedToggleEvent<HTMLDetailsElement>) => {}; | ||
<dialog onToggle={(e) => ({ newState: e.newState, oldState: e.oldState }) } />; | ||
createElement('dialog', { onToggle: onToggle }); | ||
h('dialog', { onToggle: onToggle }); | ||
|
||
// Should default to correct event target element for the attribute interface | ||
h<JSX.InputHTMLAttributes>('input', { onClick: e => e.currentTarget.capture }); | ||
|
Oops, something went wrong.
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.
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.
We've never done this before (to my knowledge), but maybe it's a viable strategy? It's not too gnarly and hopefully with the blocks it can be removed in the future pretty easily.
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.
looks good to me. Admittedly I'm not even sure if we've settled on a particular TS version to support.
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.
We haven't, though we do have split types for supporting >5.1 & <5.1 at the moment.
Issue is that every time we've bumped up the minimum people in other communities have had problems -- unfortunate side effect of being popular for widgets & component libs. IIUC, Angular still restricts TS versions per (Angular) major, for example.