[MAGNOLIA-8456] Extract NodeNameHelper common logic Created: 09/Jun/22  Updated: 13/Jun/22  Resolved: 13/Jun/22

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: Improvement Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Lam Nguyen Bao
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
clones PAGES-610 [SaaS] Reimplement Create action on t... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MAGNOLIA-8457 Development Sub-task Closed Lam Nguyen Bao  
MAGNOLIA-8460 PiQA Sub-task 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: TPR SaaS Norsu Pages
Sprint: AuthX 11
Story Points: 0
Team: AuthorX

 Description   

With the addition of norsu, unique names should be provide agnostic of the underlaying db.

The jcr logic should be extracted out of this so that norsu implementation can implement the parent class and not duplicate the common code


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