[MGNLFE-106] In Vue library when adding a component to an area it is added to a subpage if it has the same area Created: 04/Aug/21  Updated: 17/Sep/21  Resolved: 26/Aug/21

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.0

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Canh Nguyen
Resolution: Fixed Votes: 0
Labels: VN-Analysis, VN-Implementation, VN-Testing
Remaining Estimate: 0d
Time Spent: 5.75d
Original Estimate: 0d

Attachments: GIF File same-component-1.gif    
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: External SPA
Sprint: HL & LD 35, HL & LD 36
Story Points: 3

 Description   

Steps to reproduce: 

When deleting one of newly added component(either in main or sub-page), the other is removed as well.

Note: Could it be related to area improvement?

Does not happen with React.

Check if impacts Angular



 Comments   
Comment by Canh Nguyen [ 23/Aug/21 ]

The issue is that vue didn't clear old components completely when switching pages that had same a page template. By adding keys to areas, components, the issue is fixed.

Generated at Mon Feb 12 05:44:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.