Details
-
New Feature
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
Description
Revised:
The mongo/options package uses chained-setters for constructing options. But types referenced by mongo/options, such as WriteConcern, ReadConcern, etc., are constructed with functional options style. Mixing styles confuses users and could be revised/replaced for consistency.
Additionally, some types are defined within mongo/options (such as Credential, Collation, etc.) but others have their own package (e.g. readpref.ReadPref, etc.). There is no obvious guide for what to expect to find where.
Original:
specifying writeconcern is difficult and confusing, and doesn't conform with the idiom established for options in the driver. It should be specifiable, perhaps with its own options type.
Attachments
Issue Links
- is duplicated by
-
GODRIVER-2034 API Consistency for read/write
-
- Closed
-
- related to
-
GODRIVER-2689 Simplify the "readpref" API
-
- Backlog
-
-
GODRIVER-2685 Simplify "writeconcern" API
-
- Closed
-
-
GODRIVER-2686 Simplify "readconcern" API
-
- Closed
-