Refactor command error handling

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.4
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • Platform 4 06/05/15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Right now we catch AssertionException/UserException multiple times and duplicate the same logic for generating error responses throughout the command execution pipeline.

      We should make one method to generate an error reply, and let all exceptions bubble up to a canonical place where it is called.

            Assignee:
            Adam Midvidy (Inactive)
            Reporter:
            Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: