Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-6196

Map2Bean should keep track of conversion problems, so that we can report them in definitions app

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • 5.5
    • None
    • configuration
    • None
    • Saigon 15, Basel 50, Basel 52
    • 13

      Currently, if a yaml file is loaded with a property that doesn't exist in the corresponding class, we simply log the problem and continue. Ideally, we'd like to keep track of those problems to be able to report them in the config app. They should not necessarily prevent the file from being loaded, but it is likely a user error, such as a typo, that leads to this, so users should be warned.

      Just logging it seems weak, considering that we have better error handling capabilities in the new config api and app. The current log is particularly weak, since it can't report where the unknown property comes from (what file, for which definition, which registry, etc)

      + we could perhaps do the same thing in node2bean.

        Acceptance criteria

              apchelintcev Aleksandr Pchelintcev
              gjoseph Magnolia International
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoD

                    Estimated:
                    Original Estimate - 0.5d Original Estimate - 0.5d
                    0.5d
                    Remaining:
                    Remaining Estimate - 0d
                    0d
                    Logged:
                    Time Spent - 24d 4.5h
                    24d 4.5h