[GODRIVER-2139] Regex decoding error tests in top.json have unexpected, invalid syntax Created: 26/Aug/21 Updated: 28/Oct/23 Resolved: 28/Jul/23 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.12.1 |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Qingyang Hu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Documentation Changes: | Not Needed | ||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||
| Description |
|
Downstream changes: drivers should sync their BSON corpus spec tests to mongodb/specifications@5fad277. Two regex tests within top.json's decodeErrors array have changed. SummaryTwo decodeErrors tests in top.json incorrectly use $options as a field within $regularExpression. That causes a parsing error, which can interfere with the actual error being expected by the test (using a number instead of a string for pattern or options). This error dates back to mongodb/specifications@c6d7ac8. MotivationWho is the affected end user?Driver test suites may not be properly testing expected types for $regularExpression syntax in Extended JSON. Is this issue urgent?No. Is this ticket required by a downstream team?No. Is this ticket only for tests?Yes. |
| Comments |
| Comment by Githook User [ 01/Aug/23 ] |
|
Author: {'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}Message: |
| Comment by Githook User [ 28/Jul/23 ] |
|
Author: {'name': 'Qingyang Hu', 'email': '103950869+qingyang-hu@users.noreply.github.com', 'username': 'qingyang-hu'}Message: |