Update for-in loop snippet with Object.hasOwn()
#262682
Merged
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
Contributor
Author
|
@microsoft-github-policy-service agree |
mjbvz
approved these changes
Aug 21, 2025
Collaborator
mjbvz
left a comment
mjbvz
left a comment
There was a problem hiding this comment.
Thanks yes seems widely enough supported at this point to switch
TylerLeonhardt
approved these changes
Aug 21, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Cleaner change for the For-In Loop snippets. With an early continue for 1 less indent & does not trigger ESLint no-prototype-builtins
I used
Object.hasOwn(${2:object}, ${1:key})over${2:object}.hasOwn(${1:key})because the latter only showed "any" in the hover poup while the former gives the method's documentation from theObjectConstructortypescript interface.Closes #262678