Story #15336

[Workbench2] Logging

Added by Eric Biagiotti 6 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Develop an approach for logging workbench 2 events/errors. Maybe something like this: https://github.com/LogRocket/redux-logger

For making async/API calls, the general pattern is to dispatch actions for starting the request, a successful request, and a failed request. This will ensure that the sequence of redux actions accurately describes how the app is being used. We can then take advantage of tools that automatically log actions/state in production.


Related issues

Related to Arvados - Story #15333: [Epic] Workbench2 has reached feature parity with Workbench, so that that latter can be deprecatedNew

History

#1 Updated by Eric Biagiotti 6 months ago

  • Related to Story #15333: [Epic] Workbench2 has reached feature parity with Workbench, so that that latter can be deprecated added

#2 Updated by Eric Biagiotti 6 months ago

  • Subject changed from Workbench 2 logging to [Workbench2] Logging

#3 Updated by Tom Morris 4 months ago

  • Target version set to To Be Groomed

#4 Updated by Eric Biagiotti 3 months ago

  • Description updated (diff)

Also available in: Atom PDF