Audit invariants in Repl code base to add more information

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Throughout our code, we have some invariants like this one that test multiple conditions and throw if any of them are triggered. In cases where this does throw, it can be difficult to initially understand exactly how the invariant is triggering.

      We should audit our multi-condition invariants throughout our code and separate them if possible. For the invariants that cannot be separated, we should add a comment that can provide some additional info and make debugging easier

            Assignee:
            Unassigned
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: