When validating an invalid migration plan, an exception containing all detailed errors is thrown

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Duplicate
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: engine

      When validating, don't stop and throw an exception on the first violation but collect all violations and throw an exception that identifies them all (similar to Bpmn parser). Easier for users to correct their migration plans. The exception may also contain a structured error report that can be transformed to JSON in the REST API such that validation errors can be shown in Cockpit.

            Assignee:
            Unassigned
            Reporter:
            Thorben Lindhauer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: