-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
refactor: Reorganize transformInteriorValue #9566
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: alpha
Are you sure you want to change the base?
Conversation
I will reformat the title to use the proper commit message syntax. |
🚀 Thanks for opening this pull request! |
9ec6cfd
to
d4c3acf
Compare
This code was checking a constantly true condition value !== CannotTransform, that's why the code was not properly handling nested structure properly, The code introduced by parse-community#8446 fixed this logic, by introducing another duplicated piece of code. This commit simplifies the logic here to reflect the original purpose.
This PR should also fix the (broken since #8446) |
@kassiansun Thank you for the PR, and you patience in waiting for review. I've rebased it and restarted the CI. |
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.
You removed a few handling cases, what is the purpose of this, shouldn't the removed cases be handled as well?
These cases are handled later in the function, the logic was duplicated twice |
Could you provide more details? Where are they handled? |
Pull Request
Issue
This code was checking a constantly true condition value !== CannotTransform, that's why the code was not properly handling nested structure properly, The code introduced by #8446 fixed this logic, by introducing another duplicated piece of code.
Closes: #9567
Approach
This commit simplifies the logic here to reflect the original purpose.