[CSHARP-3820] Regex decoding error tests in top.json have unexpected, invalid syntax Created: 26/Aug/21 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | C# Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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. |