docs: Switch TS Events docs to use .currentTarget#1241
Merged
rschristian merged 1 commit intomasterfrom Feb 18, 2025
Merged
Conversation
JoviDeCroock
approved these changes
Feb 18, 2025
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
2 participants
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.
Something that's popped up a few times in the last few days, we should generally point users to
.currentTargetnow that our types will infer the correct element automatically when possible. Impossible to avoid casting with.targetwhich is a bit cumbersome.Not sure if we should explicitly state why
.currentTargetshould be preferred over.target, or at least, I'm not sure how to phrase that beyond "React does weird things with their events".