[SERVER-48886] Make VectorClock::isEnabled() internal Created: 16/Jun/20 Updated: 06/Dec/22 Resolved: 21/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin Pulo | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
Currently the isEnabled() method in VectorClock is public, because various external places need to know whether or not the vector clock is enabled. It would be better (from a code coupling/cohesion POV) if iEnabled() was only used from within VectorClock class (and closely related classes). Current uses:
|