refactor: Use object.prototype to check for reserved properties #5670
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.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Description:
This PR includes the following improvements:
Refactoring the use of the
in
operator: Replaced the use of thein
operator on an empty object{}
withObject.prototype
to properly check ifparts[0]
is a property of JavaScript's built-in objects. The previous approach always returnedfalse
, making the check ineffective.Optimization of null assignment logic: When
isReserved
istrue
, assigningnull
toparts[0]
was unnecessary. Instead,parts[0]
is now retained to avoid redundant null assignments and improve the overall logic.