[x] I documented the TypeScript code using JSDoc style.
Motivation and Context
Updating redux state with the movement of elements can cause problems when there are many elements on the page. With this change we are updating redux state at the end of the movement when there are many elements. Number of elements is determined according to cpu power of the user.
Description
Added cpu performance measure at the beginning
Moved element position change to state when there are many elements
Removed unnecessary state duplication from reducers
Used animationframe instead of debounce for updating movement on mouse move
Steps for Testing
Place elements on the screen and move them
Performance tab of Google dev tools can be used, it also allows you to add cpu throttle
Checklist
Motivation and Context
Updating redux state with the movement of elements can cause problems when there are many elements on the page. With this change we are updating redux state at the end of the movement when there are many elements. Number of elements is determined according to cpu power of the user.
Description
Steps for Testing