Skip to content

fix(multiple): replace hasOwnProperty with Object.hasOwn - #33843

Merged
crisbeto merged 1 commit into
angular:mainfrom
crisbeto:has-own-property
Sep 21, 2026
Merged

crisbeto merged 1 commit into
angular:mainfrom
crisbeto:has-own-property

Conversation

@crisbeto

Copy link
Copy Markdown
Member

Replaces all the usages of hasOwnProperty with Object.hasOwn since the latter handles some edge cases better. We went through this exercise on the framework repo some time ago.

Replaces all the usages of `hasOwnProperty` with `Object.hasOwn` since the latter handles some edge cases better. We went through this exercise on the framework repo some time ago.
@crisbeto crisbeto added the target: rc This PR is targeted for the next release-candidate label Sep 20, 2026
@pullapprove
pullapprove Bot requested a review from josephperrott September 20, 2026 09:16
@crisbeto
crisbeto requested a review from ok7sai September 20, 2026 09:16
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 21, 2026
@crisbeto
crisbeto merged commit 508b45a into angular:main Sep 21, 2026
29 of 32 checks passed
@crisbeto

Copy link
Copy Markdown
Member Author

This PR was merged into the repository. The changes were merged into the following branches:

crisbeto added a commit that referenced this pull request Sep 21, 2026
Replaces all the usages of `hasOwnProperty` with `Object.hasOwn` since the latter handles some edge cases better. We went through this exercise on the framework repo some time ago.

(cherry picked from commit 508b45a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants