I've been getting a bit inconsistent with my phrasing around the HeartbeatMaintainer class. At a high level, it is very similar to the IdempotencyMonitor: Both monitor watched jobs to do upkeep on them. Recently, I have been also referring to HeartbeatMaintainer as a monitor. The problem is, that might not necessarily be as intuitive to others as it is to me with my familiarity with the template. So, we need to pick a lane.
Between 'Maintainer' and 'Monitor', I like 'Monitor' better. 'Monitor' is a better fit for the idempotency system, too.
Ending my current session shortly, but marking this ToDo for later:
- Rename
HeartbeatMaintainer to HeartbeatMonitor
- Track down any surviving mentions of a maintainer, switch wording to monitor.
Marking this as a documentation issue because there are absolutely no functional changes.
I've been getting a bit inconsistent with my phrasing around the
HeartbeatMaintainerclass. At a high level, it is very similar to theIdempotencyMonitor: Both monitor watched jobs to do upkeep on them. Recently, I have been also referring toHeartbeatMaintaineras a monitor. The problem is, that might not necessarily be as intuitive to others as it is to me with my familiarity with the template. So, we need to pick a lane.Between 'Maintainer' and 'Monitor', I like 'Monitor' better. 'Monitor' is a better fit for the idempotency system, too.
Ending my current session shortly, but marking this ToDo for later:
HeartbeatMaintainertoHeartbeatMonitorMarking this as a documentation issue because there are absolutely no functional changes.