-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: TypeError on creating properties on immutable objects #671
Open
novikovfred
wants to merge
5
commits into
edmundhung:main
Choose a base branch
from
novikovfred:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+27
−1
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
11fab87
fix: type error, cannot create property
novikovfred a5d570e
Empty-Commit
novikovfred 47437e4
fix: type error, cannot create property
novikovfred 85f85dd
fix: type error, cannot create property
novikovfred 69395d2
Merge pull request #1 from novikovfred/fix_typeerror
novikovfred File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
I wanna understand better the impact of this change. Can you explain a bit more what each condition is trying to handle?
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.
As i mentioned in #670 (we can reproduce with FormData as well)currently we can get TypeError if we will try to assign property on immutable object.
Since we validate and get data from those parameters that can be passed by users, including frauders. We wouldn't want to get errors in runtime error because of a user who enters intentionally incorrect data.
If frauder will try to create any param with immutable type at first(example:
param=value
) and then will try to add some property to it (example:param.child=value
) we will get a TypeError.Of course, I can handle the error, but I would like not to get errors in the application's runtime.
If we wanna support changes of property values i can rework my PR a bit.
With these change I want to check properly if we can add a property to a given object.