Transition guide for using mouse/touch events from 1.x to 2.x. #27
Conversation
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
README.md
Outdated
|
|
||
| Instead, in 2.x you can use the key function to directly compare the key value. | ||
| ```js | ||
| if (key === 'Enter') { // Enter key |
There was a problem hiding this comment.
Since you’re referencing key here, would it be possible to briefly mention the related change involving code as well? While it’s not currently documented on the reference page, you can refer to the PR I created: #7902 for context.
|
@perminder-17 I have added code as well, can you review it again and let me know if I need to add something else? |
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.
Updated Readme to provide transition guide for using mouse/touch events from 1.x to 2.x. (also fixed a minor grammatical error)
closes #23