You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since transformInteriorValue 4d43614, the code never trigger the logics after value !== CannotTransform. This bug was noticed and fixed in #8209 in a wrong way, and later #8446 introduced a (partially) corrected but duplicated fix.
Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
Parse Server version: 7.4.0
Operating system: Ubuntu
Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): AWS
Database
System (MongoDB or Postgres): MongoDB
Database version: 5.0.18
Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): AWS
🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.
Is this a bug, or just a code refactoring without any effects on performance or behavior?
I didn't test it, but I think the RegExp and Bytes are all broken since #8446, because if (value && typeof value === 'object') { will be true for both, so the value saved in database will be a JSON-serialized version of mongodb.Bytes and mongodb.RegExp (or not broken if mapValues(restValue, transformInteriorValue) doesn't change the value of the object, but this is a coincidence instead of an explicit specified behavior).
Also this logic is handled properly after #9566, which is a definitely a behavior change (although it's from the original refactoring, but it never triggered since that):
New Issue Checklist
Issue Description
Since transformInteriorValue 4d43614, the code never trigger the logics after
value !== CannotTransform
. This bug was noticed and fixed in #8209 in a wrong way, and later #8446 introduced a (partially) corrected but duplicated fix.Steps to reproduce
Actual Outcome
Expected Outcome
Environment
Server
7.4.0
Ubuntu
AWS
Database
MongoDB
5.0.18
AWS
Client
JavaScript
5.3.0
Logs
The text was updated successfully, but these errors were encountered: