Skip to content
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.

Undefined identifier during component refresh #200

Open
1 of 4 tasks
StephenEsser opened this issue Feb 18, 2019 · 0 comments
Open
1 of 4 tasks

Undefined identifier during component refresh #200

StephenEsser opened this issue Feb 18, 2019 · 0 comments
Labels
new-relic Errors uncovered from new-relic monitoring

Comments

@StephenEsser
Copy link
Contributor

Issue Description

A refresh call is being made to an undefined component. This is likely due to queued undo / redo actions. We should prevent a user from stacking multiple refresh actions into a queue.

https://github.com/cerner/kaiju/blob/master/rails/client/app/bundles/kaiju/components/Component/utilities/dispatcher.js#L97

Error

undefined is not an object (evaluating 'fetch(id).url')

Issue Type

  • New Feature
  • Enhancement
  • Bug
  • Other

Expected Behavior

Multiple refresh actions should not be queued. A new action should wait until the previous action is completed to prevent a call to refresh on an undefined component.

Current Behavior

The redux store may no longer contain a component and throws an error.

Steps to Reproduce

  1. Create a workspace
  2. Add multiple components into the workspace
  3. Repeatedly use the keyboard shortcuts for undo / redo
  4. Observe the refresh eventually throws an error.
@StephenEsser StephenEsser added bug new-relic Errors uncovered from new-relic monitoring labels Feb 18, 2019
@ryanthemanuel ryanthemanuel removed the bug label May 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-relic Errors uncovered from new-relic monitoring
Projects
None yet
Development

No branches or pull requests

2 participants