does not work with immutable.js object as state
See original GitHub issueDue to object destructuring in createStore
immutable.js objects are losing some of their methods, e.g. Map
loses getIn
, setIn
etc.
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Using an ImmutableJS Object as the React Component State
state.get is not a function. Below is a minimal example to reproduce the error. Every time the increment button is pushed, the count...
Read more >does not work with immutable.js object as state #31 - GitHub
In redux it is fine to use immutable because the state is not manipulated directly. And more: if we want to use immutable...
Read more >Immutable.js - Basics | David Tanzer - Coach Consultant Trainer
When changing the read-only state, you are not allowed to mutate the existing object: You are supposed to create a new object.
Read more >React, Redux, and Immutable.js: Ingredients for Efficient UI
According to official documentation reducer function in Redux should always emit a new state object using Object.assign(), so why is there need for...
Read more >How To Use Immutable.js in a React Redux Application
One of the key requirements of redux is that each reducer must be pure. That is given a state and an action it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No problem, thank you guys for such a great library! 👍
Thank you @Yevs
And we get back to this, I’ll make sure you’re involved.
💯