[PAGES-253] Decouple PageContentClipboardConstraint from PageContentClipboard Created: 05/Mar/20  Updated: 23/Aug/22

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Unresolved Votes: 0
Labels: None
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)
Team: AuthorX

 Description   

Currently PageContentClipboardConstraint depends on PageContentClipboard to decide whether a node can be moved to a certain destination by evaluating the available templates. We should remove this dependency and make both classes depend on a common utility that does the evaluation of the templates.

Furthermore we should consider moving the check for deleted nodes to the super class (JcrClipboard).


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