Adding autoRehydrate() > One of the sources for assign has an enumerable key on the prototype chain. This is an edge...
See original GitHub issueHi,
I am facing this error message :
One of the sources for assign has an enumerable key on the prototype chain. This is an edge case that we do not support. This error is a performance optimization and not spec compliant.
Here is my code to create store :
const middlewares = [
sagaMiddleware,
thunk
];
const enhancers = [
applyMiddleware(...middlewares),
autoRehydrate()
];
if (__DEV__) {
enhancers.push(devTools());
}
const store = createStore(
createReducer(),
{},
compose(...enhancers)
);
// react-native
persistStore(store, {storage: AsyncStorage});
// Extensions
store.runSaga = sagaMiddleware.run;
Does anyone have an idea for solution please ? Thanks
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
One of the sources for assign has an enumerable key ... - GitHub
1 ) I started getting an error: One of the sources for assign has an enumerable key on the prototype chain. Are you...
Read more >React Native Enumerable key on prototype chain error
Im trying to upload an base64 image to the Firebase Storage with and getting this error: One of the sources for assign has...
Read more >omnidan/redux-undo - Gitter
I'm running into this error: One of the sources for assign has an enumerable key on the prototype chain. This is an edge...
Read more >Link to Other Objects through the JavaScript Prototype Chain
In this lesson we'll test this out by adding properties and working with this linkage of properties. illustration for Understanding JavaScript's ...
Read more >What is __proto__ ? | Javascript Prototypes Tutorial - YouTube
What is __proto__ ? This Javascript prototypes tutorial will help you understand Javascript prototype inheritance and the prototype chain.
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 Free
Top 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
If you’re using immutable.js like me for your store, try swapping redux-persist to redux-persist-immutable, that fixed it for me. import {persistStore, autoRehydrate} from ‘redux-persist-immutable’
https://github.com/rt2zz/redux-persist-immutable
👍
Open to suggestion / PR for how to detect this scenario and display better error messages. In the meantime I believe this is solved.