[MGNLUI-8001] Author shouldn't be able to create too many items at the same level Created: 19/Apr/23  Updated: 13/Sep/23

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

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
documentation
to be documented by PUBLISHING-294 Create a recommendation for structuri... 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)
Epic Link: Performance problems with too many child nodes
Team: Nucleus

 Description   

Steps to reproduce

  1. Create thousands of child nodes.
  2. Expand the parent node.
  3. Publish recursively the parent node.
  4. ....

Expected results

The data, user is allowed to create, shouldn't cause major performance issues.

User should be prevented or notified about the performance limitation.

Actual results

User can create as many child nodes as she wants.

Workaround

Evangelise the users regarding the proper data structure.

Development notes

There might be different way to improve the situation

  • addNodeAction (or other actions creating content) could warn the user (notification) if the child count exceeds the configurable threshold
  • addNodeAction (or other actions creating content) could warn the admin (log) if the child count already exceeds the configurable threshold
  • ...

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