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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using
result.hasOwnProperty(key)directly on an object can lead to runtime errors or unexpected behavior if the query parameters contain keys that match prototype properties (e.g.,hasOwnProperty,toString). For example, if a query parameter ishasOwnProperty=123,result.hasOwnPropertywill be overwritten, and subsequent calls toresult.hasOwnProperty(key)will throw aTypeError: result.hasOwnProperty is not a function, crashing the application.To prevent this, use
Object.hasOwn(result, key)(orObject.prototype.hasOwnProperty.call(result, key)).Additionally, please note that this function is duplicated in
packages/lib/fromEntriesWithDuplicateKeys.ts. You should apply the same fix there, or ideally, refactor the code to importfromEntriesWithDuplicateKeysfrom a single shared location to avoid duplication.