beat.editor issueshttps://gitlab.idiap.ch/beat/beat.editor/-/issues2018-07-26T17:52:14Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/124State management refactoring2018-07-26T17:52:14ZJaden DIEFENBAUGHState management refactoringThought we already had an issue open for this but I guess not.
Right now the object editors are using a `cache` state field to hold the unsaved changed. These changes aren't propogated to the redux store until the user clicks 'save', wh...Thought we already had an issue open for this but I guess not.
Right now the object editors are using a `cache` state field to hold the unsaved changed. These changes aren't propogated to the redux store until the user clicks 'save', which will *also* save to the prefix. There's no reason to have a state cache and the redux store anymore.
Instead of using the editors' states' cache fields to store unsaved changes, just use the redux store!State Management Refactoringhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/111Refactor out the throttling/debouncing code2018-08-06T14:47:52ZJaden DIEFENBAUGHRefactor out the throttling/debouncing codeI'm thinking just adding `lowdash.throttle` as a dep and having a simple wrapper:
```js
export const throttle = _.throttle;
```I'm thinking just adding `lowdash.throttle` as a dep and having a simple wrapper:
```js
export const throttle = _.throttle;
```State Management Refactoringhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/113Faster/more secure object deep copy with libraries2018-07-26T17:52:14ZJaden DIEFENBAUGHFaster/more secure object deep copy with librariesMaybe use https://github.com/planttheidea/fast-copy instead of just my weird cloning via object spread operatorMaybe use https://github.com/planttheidea/fast-copy instead of just my weird cloning via object spread operatorState Management Refactoring