Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-1965

API design for deletion prevention

    XMLWordPrintable

Details

    • Core: Platform

    Description

      In order to support the following user experience during deletion, with usage checks implemented in the backend

      1. click delete
      2. present modal to disallow if in use
      3. otherwise present confirmation modal
      4. attempt to delete if confirmed

      At the moment, the checks for usage tend to be performed by the UI.

      We need to decide:

      • What is the API for checking that a record is in-use or not (e.g. endpoint structure, responses etc)?
      • How do we provide a client meaningful response to explain why a delete fails?
      • How do we check for usage (especially when usage could be in other modules / contexts)?

      Assumptions

      • Usage checks for in use will be performed during DELETE endpoint execution, as well as the mechanism we decide upon to check before issuing the delete.

      Context

      Some conversation around this topic has already happened on CIRC-179, CIRCSTORE-121 and UICIRC-185

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                marcjohnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases