Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3753

When a required for field encounters value conversion exception - the stacktrace is pushed to the error message

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Neutral
    • None
    • 5.4.4
    • None

    Description

      As of resolution of a linked issue - the form fields attempt to commit the invalid values to the backend, which results in this:

      We need to investigate whether the workaround for MGNLUI-2774 is still required (cause for me it looks like it doesn't make a lot of sense). Suppressing it would prevent invalid values to be attempted to be written to the property data-source and error messages would look nice and clean.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                apchelintcev Aleksandr Pchelintcev
                Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD