[MGNLUI-1472] Content app should launch without actionbar configuration Created: 29/May/13  Updated: 28/Jun/13  Resolved: 27/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: 5.0
Fix Version/s: 5.0.1

Type: Bug Priority: Major
Reporter: Antti Hietala Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

5.0 beta 2


Issue Links:
relation
is related to MGNLUI-1723 Incomplete app definition breaks the ... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

A content app does not launch unless you configure an action bar. This is too much to ask. When you configure your first content app step-by-step, you have to create a lot of configuration before you can see the app run for the first time.

  1. Configure the app classes
  2. Add the app to the launcher
  3. Configure a browser subapp
  4. Configure a workbench
  5. Add columns to the workbench
  6. Configure actions
  7. Configure an action bar

Make the threshold lower. Give new users the "whoa it works" feeling faster. Make the app launchable after step 3. Even if it just displays an empty subapp.

The system can handle a missing actionbar definition already today.

WARN: No actionbar definition found. This will result in an empty action bar. Is that intended?

So maybe it is just the configured content app that fails to start.


Generated at Mon Feb 12 08:46:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.