Allow statuses/assertions to have both a named error code and a unique number

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently statuses/assertions can have either a named error code or a unique number. Named error codes are useful for cases which are semantically the same from the user's point of view. However for diagnosability/debuggability, unique numbers can be very helpful because you can immediately tell exactly where an error came from. So it might be nice to be able to include a unique number together with a named code, for instance in a uassert.

              Assignee:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: