[MGNLUI-3435] Prevent app failures, add warnings when configuration is incomplete Created: 21/May/15  Updated: 02/Jun/15  Resolved: 21/May/15

Status: Closed
Project: Magnolia UI
Component/s: content app, workbench
Affects Version/s: 5.3.8
Fix Version/s: 5.4

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: configuration, content-app, resources-app
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

I faced several issues/app crashes while developing the new resources app (content app), due to "work in progress" incomplete configuration.
I think we can be more tolerant there, as well as we can improve reporting of potential problems. Not knowing what goes wrong typically requires time to debug.

Here are some sample problems that occurred:

  • NullPointerExceptions due to missing definitions (triggers the "failed app" view)
  • Lack of information when we expect some configuration constraints, e.g. 1-to-1 mappings between action names under actionbar and actions configuration.
  • Lack of "degrading" strategies (e.g. incorrect ColumnDefinition)


 Comments   
Comment by Mikaël Geljić [ 21/May/15 ]

Resolved on branch feature/resources-app

Generated at Mon Feb 12 09:06:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.