-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
Deprecating legacy timeout options with the addition of Timeout to ClientOptions has left some users with static analysis failures (deprecation warnings) and no stable alternative (as Timeout is still provisional API). We should wait until CSOT is more stable before doing GODRIVER-2342. For now, let's change the Deprecated: notices to NOTE sections that suggest using Timeout in place of the given legacy timeout option.
- has to be done before
-
GODRIVER-2342 Deprecate SocketTimeout, wTimeout, MaxTime and MaxCommitTime
- Closed