Simplest fix is to remove this validation for 2.6.0 (only). See WriteConcernOptions::parse().
Strict validation of j / fsync to be boolean is backwards-breaking for some drivers
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: