Do not store original OpObserver functions in TransactionParticipantTests

XMLWordPrintableJSON

    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have a pattern where we save the original OpObserver override function and then call it from the new one. This is unnecessary since anything in the original can just be in the actual mock function, and the originals are currently noops.

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: