-
Notifications
You must be signed in to change notification settings - Fork 2.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
[core] feat(InputGroup): new prop onValueChange
#6290
Merged
adidahiya
merged 5 commits into
palantir:develop
from
thasner:th/input-group-value-change
Jul 25, 2023
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9018847
Add onValueChange to InputGroup
thasner d5b3ebb
Update packages/core/src/components/forms/inputGroup.tsx
thasner 86881c0
complete implementation, fix lint
adidahiya 1e6d3ad
use new prop in codebase
adidahiya 4590759
add unit test
adidahiya 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
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 |
---|---|---|
|
@@ -58,8 +58,8 @@ export class Icons extends React.PureComponent<IconsProps, IconsState> { | |
className={Classes.FILL} | ||
large={true} | ||
leftIcon="search" | ||
onValueChange={this.handleFilterChange} | ||
placeholder="Search for icons..." | ||
onChange={this.handleFilterChange} | ||
type="search" | ||
value={this.state.filter} | ||
/> | ||
|
@@ -100,10 +100,7 @@ export class Icons extends React.PureComponent<IconsProps, IconsState> { | |
return icons.filter(icon => iconFilter(this.state.filter, icon)); | ||
} | ||
|
||
private handleFilterChange = (e: React.SyntheticEvent<HTMLInputElement>) => { | ||
const filter = (e.target as HTMLInputElement).value; | ||
this.setState({ filter }); | ||
}; | ||
private handleFilterChange = (filter: string) => this.setState({ filter }); | ||
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. nice |
||
} | ||
|
||
function isIconFiltered(query: string, icon: Icon) { | ||
|
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
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
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.
I wasn't sure if it'd be reasonable to ban native
onChange
usage, let alone make such a breaking change.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.
No, we won't ban it, and we can't make a breaking change like that right now. We can just update the docs and maybe create a lint rule.
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.
Event pooling is going away in React 17, so I think this will become less of a problem: https://legacy.reactjs.org/blog/2020/08/10/react-v17-rc.html#no-event-pooling
I added a note in the JSDoc for the new prop about why users might prefer this handler instead of
onChange
.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.
sounds good.
imo the
onValueChange
signature is also an ergonomic improvement, so i anticipate it'll still have usage