Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Immutable JS broken on V3

See original GitHub issue

Looks like LocalizeProvider immutable stores are not supported, if store is a Map then localize should be retrieved using get('localize'):

const curLocalizeState = this.props.store.getState().localize;

See:

https://github.com/ryandrewjohnson/react-localize-redux/blob/master/src/LocalizeProvider.js#L73

Issue Analytics

State:
Created 5 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

gabroecommented, Jun 6, 2018

Got it, I’ll work on it hopefully this week!

0reactions

thchiacommented, Jun 20, 2018

@ryandrewjohnson yup that was what I was thinking regarding the prop on the Provider.

I probably won’t be able to do anything till the weekend so if you want to jump in before that please do 😄 .

Top Results From Across the Web

Issues · immutable-js/immutable-js

Mutating the [[Prototype]] of an object will cause your code to run very slowly; awaiting-response Awaiting response from creator. Can't fix without it....

Immutable.js setIn not working

The issue is that questions is an Immutable List of vanilla JS objects. List#setIn() only works on deeply immutable objects. You probably want ......

immutable.js-flow-fix

Immutable data cannot be changed once created, leading to much simpler application development, no defensive copying, and enabling advanced ...

Documentation v4.2.1 — Immutable.js

The hash() function is an important part of how Immutable determines if two values are equivalent and is used to determine how to...

The Case for Immutability in JavaScript | by Fernando Doglio

Notice that all I did was change line 3 by creating a List with my original ... We can also fix that issue...