-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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(Search): fix event passed to onChange
when clearing input (#12133)
#12140
Merged
kodiakhq
merged 6 commits into
carbon-design-system:main
from
gi:issue-12133/search-clear-click-onchange
Oct 4, 2022
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ceffc91
fix(Search): fix event passed to `onChange` when clearing input (#12133)
gi 970b11d
Merge branch 'main' into issue-12133/search-clear-click-onchange
gi b034bde
Merge branch 'main' into issue-12133/search-clear-click-onchange
gi 552dc50
test(Search): update mock onchange to check only value
gi 28360aa
fix(Search): use input element as target in onChange event on clear
gi 5365473
Merge branch 'main' into issue-12133/search-clear-click-onchange
kodiakhq[bot] 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
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.
Should this be in a
beforeEach
orbeforeAll
?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 could be a
beforeAll
, but that would only be doing the same thing as this but with less clarity: the functions would need to be declared aslet
variables and then assigned in thebefore
routine.This code solves for an issue that I see a lot with front-end tests and which I see with the tests in this suite: if you render the element under test in a
beforeEach
routine, then it makes any other setup in nested contexts very difficult. You end up with multiple renders of the element.In fact, I believe that some of the tests in this suite are finding the wrong element rendered.
If you move the mounting or rendering into each test/
it
, then you avoid this issue.To avoid duplicating the possibly complex mount/render declaration, I have adopted this paradigm which works quite well in my experience.
Each nested context/describe can build on the props:
Each test simply becomes