Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-39797

Always catch exceptions in processFormattedText

    XMLWordPrintable

    Details

    • Type: Task
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.6.x, 2.7.x
    • Fix Version/s: 2.7.x, 2.8.x
    • Component/s: Kernel
    • Labels:
      None

      Description

      KNL-66 is an example of a processing error which formattedText is susceptible to. While all these cases should be fixed, in the event that there is some failure in the handling code that generates an exception, it is better to catch the exception and return an appropriate error message rather than let the exception propagate.

      This will usually give the user the opportunity to retry with different text to possibly workaround the issue, rather than throwing a stack trace in the tool which may cause loss of data being input.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  smarquard Stephen Marquard
                  Reporter:
                  smarquard Stephen Marquard
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration