[STCOR-650] remove service-point handling - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Task
Status: Closed (View Workflow)
Priority: P3
Resolution: Done
Affects Version/s: None
Fix Version/s: 9.0.0
Labels:
- breaking_change

Template:
Sprint:
stripes-force 151, stripes-force 156, stripes-force 157
Development Team:
Stripes Force
Release:
Orchid (R1 2023)
RCA Group:
TBD

Description

Summary: stripes-core does not depend on the inventory Okapi interface; thus it must not contain logic related to data derived from this interface.

Details: Service points leaked into stripes-core by parsing the response from /bl-users/login when its optional dependency on the inventory interface is fulfilled, but stripes-core itself does not depend on this interface and thus should not contain logic related to such data. Instead, the login response should be stored in redux and applications that do rely on inventory can use an event handler attached to the LOGIN event to retrieve that response and operate on it (e.g. ~~UISP-32~~).

Note: This will be a breaking change because setServicePoints and setCurServicePoint are publicly exported.

TestRail: Results

Attachments

Issue Links

has to be done after

STCOR-649 store raw login response details in redux

Closed

UISP-32 on login, insert service point details into the session

Closed

relates to

FOLIO-3253 SPIKE - Investigate minimal FOLIO platform

Closed

UIU-2788 refactor service-point handling in withServicePoints

Closed

Activity

People

Assignee:: Zak_Burke

Reporter:: Zak_Burke

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 26/Aug/22 7:51 PM

Updated:: 02/Feb/23 4:06 PM

Resolved:: 27/Jan/23 4:48 PM

remove service-point handling