Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: investigate problem with double call of end-point for hold shelf report

Description

When we open requests app, at first load of the page circulation/requests-reports/hold-shelf-clearance/ end-point calls twice. Also looks like it calls twice on service point change.

It's very heavy loaded operation, so we need to investigate this problem and remove unnecessary call.

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

TestRail: Results

Activity

Show:

Artem Blazhko May 11, 2022 at 10:14 AM

Additional trigger of endpoint happens because componentDidUpdate method calls setCurrentServicePointId

However, the functionality of componentDidUpdate method is correct.
To fix that issue we should change setCurrentServicePointId method. Currently, it has the following view: ** 

The issue happens because we trigger murator.currentServicePoint.update({ id }) and as a result change component service point id property, then componentDidUpdate triggers setCurrentServicePointId one more time.

To fix this issue we can try to change setCurrentServicePointId method to the following view:

 

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 19, 2022 at 8:58 AM
Updated May 12, 2022 at 12:38 PM
Resolved May 11, 2022 at 10:14 AM
TestRail: Cases
TestRail: Runs