Add support for Unsaved Changes Notification to EditableList Component

Description

This issue came up in https://folio-org.atlassian.net/browse/UIU-79:

Scenario
Given the Address type control
When I navigate away without saving changes
Then the unsaved changes notification should display per

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Charlotte Whitt August 4, 2017 at 6:14 PM

Okay, I'll close this issue then.

Michal Kuklis August 4, 2017 at 10:58 AM

I just created another issue to take care of the AddressList.

Michal Kuklis August 4, 2017 at 10:54 AM

I'm going to close this issue because I think what you tested is related to a different component (AddressList). Let's open another issue for that.

Charlotte Whitt August 4, 2017 at 9:26 AM
Edited

Manually tested in http://folio-testing.aws.indexdata.com/ version stripes-core 2.3.100692, using chrome

Hi , just tested this again. And apparently the EditableList is not applied for Users.

Steps to repro:
1. Login to FOLIO test diku_admin
2. Click on Users, select a given user A (here user id 'bernadette').
3. Click to add another address. Fill in the form.
4. Click on Items, without saving data.

Expected:
To get the usual notification saying "There are unsaved changes".

Actual:
I do not get any notification, and all entered data is lost.

Additional information:
I tried editing an item, and move away, without saving the changes. And here I get the notification.

I'll re-open the issue.

Michal Kuklis August 1, 2017 at 7:54 AM

thank you for testing this. All lists use the same component (EditableList) so they all should behave the same. Unfortunately I can't tell what version is currently deployed to http://folio-testing.aws.indexdata.com. It doesn't look like it's the newest version. It seems like a lot of other fixes are also not in place there.

Done

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created July 19, 2017 at 6:05 PM
Updated August 4, 2017 at 6:15 PM
Resolved August 4, 2017 at 6:15 PM
TestRail: Cases
TestRail: Runs