[COMPASS-7049] Investigate changes in NODE-3989: Remove deprecated boolean parsing logic in connection strings Created: 26/Jul/23  Updated: 29/Aug/23  Resolved: 29/Aug/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: PM Bot Assignee: Unassigned
Resolution: Done Votes: 0
Labels: node-driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-3989 Remove deprecated boolean parsing log... Closed
Documented
Epic Link: MONGOSH-1319
Documentation Changes: Needed
Sprint: Iteration Iguanodon

 Description   

Use Case

As a developer
I want to remove the legacy boolean options (‘1’ ‘yes’ ‘no’ etc.) from our connection string parsing
So that our options parsing is simpler and easier to work with.

User Impact

* __ Any users making use of our legacy boolean options will have to explicitly provide boolean values in connection string and MongoClient constructor

Dependencies

  • This is a breaking change, so it needs to go out in v6 of the node driver.

Unknowns

Acceptance Criteria

Implementation Requirements

  • When parsing boolean values from options in the connection string, only accept true/false as valid values.
    • Remove getBoolean helper and update relevant logic in setOption

Documentation Requirements

  • Will mark this as needs documentation changes to alert users that only explicit booleans will be accepted
  • Release notes and migration guide will mention this change

Follow Up Requirements

  • additional tickets to file, required releases, etc


 Comments   
Comment by Anna Henningsen [ 29/Aug/23 ]

Nothing to do besides docs for this one.

Generated at Wed Feb 07 22:45:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.