feat(replay): Capture keyboard presses for special characters#8051
Merged
feat(replay): Capture keyboard presses for special characters#8051
Conversation
Contributor
size-limit report 📦
|
ryan953
approved these changes
May 5, 2023
Member
ryan953
left a comment
There was a problem hiding this comment.
for initial data collection this seems reasonable. we can look for chords on the backend and see how common that is.
The way things are setup on the UI: These new categories will render in the breadcrumb list under the player. It'll have the title User keyDown
billyvg
reviewed
May 5, 2023
31c4dfd to
d6e0d09
Compare
d6e0d09 to
eea5df4
Compare
da6b84f to
acaf41a
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds a new breadcrumb for keyboard presses of special characters.
It creates a breadcrumb like this:
We do not capture this when:
inputortextareaThis way, we should hopefully only capture key combinations & special stuff, not when users are typing.
Closes #6532 (comment)