[MGNLUI-6259] ContentType based App & Column Editor's fields: 'defaultAction' can not be disabled -> key 'enter' can not be used Created: 30/Sep/20  Updated: 30/Sep/20

Status: Open
Project: Magnolia UI
Component/s: app framework, tree/list, workbench
Affects Version/s: 6.2.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-5271 ContentType based Content App's View:... Open
relates to MGNLUI-6030 Dynamic generated contentType based a... Open
relates to MGNLUI-6029 Dynamic generated contentType based a... Open
relates to MGNLUI-6040 Dynamic generated contentType based a... Open
relates to MGNLUI-6007 Dynamic generated contentType based a... Closed
relates to MGNLUI-6008 ContentType Model: "type: asset" does... Closed
relates to MGNLUI-6028 View's columns can't be ordered: Espe... 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   

Situation:

In 6.2.3 the columns editing behavior was improved.
One adaption of 'editable' on the column is:
https://documentation.magnolia-cms.com/display/DOCS62/Column+definition

optional, default is falseWhen set to true, the column can be edited inline. You can double-click a cell to edit its value. You cannot define defaultAction and use inline editing at the same time.

So the column editing can not be used as long there is a default Action defined. Which makes a lot of sense! But:

Problem:

When using a ContentType based app, the default action is always generated.
And there is no proper way to "disable"/having no defaultAction.

Workaround:

Break the autoGenerated defaultAction by adding an non existing action:

subApps:
  browser:
    actionbar:
      defaultAction: nonExisingAction

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