fix(website/omni-search): correct the usage of useEventListener
#8491
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.
Closes #8490
⛳️ Current behavior (updates)
In the
omni-search
component of the docsite, theuseEventListener
hook for the keyboard shortcut to open the search modal has incorrect arguments applied to the first two parameters, resulting in the entire hook failing.🚀 New behavior
Move the two arguments to the second and third param. The first param is looking for a target object which is not needed and can be defined
null
. The second param needs the stringkeydown
because that is the mapped event name. And the third param needs the actual event handling.📝 Additional Information
The current broken behavior will still impact the site when it shifts over to Chakra v3