-
Type: Task
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: None
-
None
Use Case
As a developer
I want the code base to not contain the offensive term "slave"
So that I don't become offended or distracted while working with the Node driver code
User Impact
Unknown
Dependencies
NODE-3788- Some of the error codes contain slaveOK in them. Completing that task first will simplify this effort.
Unknowns
- In db.ts --> can I rename `get slaveOk()` to `get secondaryOk()` or is this a public facing thing that needs to be deprecated? (How do I know what can be changed and what needs to be deprecated?)
- For related NODE-3268: Is this handled in connection.ts on line 87? I see readPreference on line 91 directly below slaveOk. Should I deprecate slaveOk on line 89? I think the other references to slaveOk() can be replaced with secondaryOK() in this file.
Acceptance Criteria
- All references to slaveOk have been removed, renamed, or moved to a constant in both src and test files.
- Any associated documentation that is automatically generated from code comments is also updated to reflect the non-offensive names
- Note: spec tests with slaveOk are being covered by
NODE-3791
Implementation Requirements
- None
Testing Requirements
- None
Documentation Requirements
- None
Follow Up Requirements
- depends on
-
NODE-3788 Update names of offensive error codes
- Closed
- is depended on by
-
NODE-4734 Remove usage of deprecated ismaster in next major release after 5.0 is min supported server version
- Backlog
-
NODE-3818 Remove usage of deprecated slaveOk in next major release
- Closed
- is duplicated by
-
NODE-3794 Rename constants with "slave" in their names
- Closed
- is related to
-
NODE-3091 Stub out Remove Oppressive Language tickets
- Closed
-
NODE-3791 Verify spec files with offensive language match the latest version
- Closed