remove service-point handling
Description
Environment
None
Potential Workaround
None
has to be done after
relates to
Checklist
hideTestRail: Results
Activity
Show:

Khalilah Gambrell October 3, 2022 at 3:27 PM
Move to Sprint 152/153

Khalilah Gambrell September 19, 2022 at 3:18 PM
A breaking change.
Done
Details
Details
Assignee
Reporter
Labels
Priority
Sprint
None
Development Team
Stripes Force
Fix versions
Release
Orchid (R1 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 26, 2022 at 7:51 PM
Updated February 2, 2023 at 4:06 PM
Resolved January 27, 2023 at 4:48 PM
TestRail: Cases
TestRail: Runs
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 theinventory
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 oninventory
can use an event handler attached to theLOGIN
event to retrieve that response and operate on it (e.g. UISP-32).Note: This will be a breaking change because
setServicePoints
andsetCurServicePoint
are publicly exported.