[MAGNOLIA-8013] Provide a delete command without deactivation Created: 16/Mar/20  Updated: 05/Mar/21

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Michael Duerig 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 PAGES-250 Cannot delete components 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)

 Description   

The current delete command is chained together with deactivation. This makes is less versatile the it could be. See e.g. PAGES-250, where this caused problems deleting components from a page.

I suggest we either add a way to configure the current delete command to skip/include deactivation or we provide separate command for deleting with activation and without it.


Generated at Mon Feb 12 04:28:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.