[SERVER-23692] Add jstest to ensure JS properties of all BSON types are read-only Created: 13/Apr/16 Updated: 08/Jan/24 Resolved: 19/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 3.3.4 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | move-stm, sdp-backlog-purge | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 13 (04/22/16) |
| Participants: |
| Description |
|
There was an API change in SpiderMonkey which might allow some properties to be non-readonly. We should verify this does not affect the Mongo shell, where all properties of BSON objects should be readonly. The API change was in response to this bug: |
| Comments |
| Comment by Alex Neben [ 19/Jun/23 ] |
|
This has been identified as work that the SDP team won't do in the near term. Please reopen with a comment if you feel this work should be reprioritized and explain why. |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |