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.
This is a discussion/brainstorm PR at this point. All thoughts are welcome.
Premise
I believe we can provide more a more usable API by bubbling more events up to the users of this component. I'm honestly not sure what those are at this point and am open to suggestions. I'm putting this PR here as a place for me to jot ideas down as I have them and collect suggestions from anyone else who has them. I think that as we work through the issues (#25) and PRs (#23) from the parent repo we might find some ideas for this as well.
Currently Documented Events
hit
input
(does this really count as an "event"?)Possible Events to Emit
enter
,esc
, arrows,tab
, etc)closed
- when the dropdown is closed