[COMPASS-7132] Updating document string value to "[object Object]" turns into empty string Created: 21/Aug/23 Updated: 29/Oct/23 Resolved: 24/Aug/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | 1.39.1, 1.39.2 |
| Fix Version/s: | 1.39.4 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Eric Dilmore | Assignee: | Maurizio Casimirri |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS: Windows 10 |
||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Description |
Problem Statement/RationaleWhen I type a string literal into the document update box, I expect that the string will accept any valid Unicode input. However, typing "[object Object]" will reset the field to an empty string when the closing brace is typed.
Other similar strings do not have this behavior. Examples are "[]", "[foobar]", and "[object Objects]".
Please be sure to attach relevant logs with any sensitive data redacted. After checking the logs, I don't see anything relevant, since the actions taken involve keypresses without sending the update. Please contact me if you have trouble reproducing. Steps to Reproduce
Expected ResultsThe new pending field value is "[object Object]". Actual ResultsThe new pending field value is "". Additional NotesWhile this is an odd document modification, it is something I was required to do to test a script to fix broken data. I am unaware if there are any other magic strings that cause similar problems. |
| Comments |
| Comment by Githook User [ 05/Sep/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 04/Sep/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 30/Aug/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 30/Aug/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 30/Aug/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 29/Aug/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Githook User [ 23/Aug/23 ] |
|
Author: {'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}Message: fix: allow [object Object] as a valid string value in TypeChecker |
| Comment by Eric Dilmore [ 21/Aug/23 ] |
|
I meant to also add my workaround, which is that this update is simple to perform by using `updateOne` in the mongo shell. The Compass interface appears to be where the problem lies. |
| Comment by PM Bot [ 21/Aug/23 ] |
|
Hello eric.dilmore@oakstreethealth.com, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible. Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again! |