[MGNLUI-3528] BrowserPresenter deletedItem handling causes exception Created: 20/Aug/15  Updated: 25/Aug/15  Resolved: 21/Aug/15

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.1
Fix Version/s: 5.4.2

Type: Bug Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLRES-186 Add create and delete actions for res... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Sprint 7 (Basel)
Story Points: 1

 Description   

While developing add and delete resource actions to resources app, i noticed the following case is throwing exception.

given(user).deletes(item);
given(action).throwsContentChangedEvent();

when(browser).refresh();

then(browser).throwsException();

This happens because the selected item cannot be found since its deleted in the transaction. Our browserPresenter should be checking if the selected is present / can be handled.



 Comments   
Comment by Ilgun Ilgun [ 20/Aug/15 ]

Changes can be found at fix/MGNLUI-3528

Comment by Mikaël Geljić [ 20/Aug/15 ]

test-case please

Comment by Ilgun Ilgun [ 21/Aug/15 ]

Test Added.

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