Clarification on Concurrent Mode Support

[samcooke98]

On the docs, specifically this page https://mobx-react.js.org/state-local there is a commen:

Note that using a local store might conflict with future React features like concurrent rendering.

Is it possible to address why this might conflict? What does conflict mean?

I've seen some discussion about React's ability to rebase, and Michel Westrate suggesting that mobx shouldn't be used for local component state - facebook/react#15317 (comment) - Is this still a valid claim still?

---

Related issues from around the place,
reduxjs/react-redux#1351 (comment)

reduxjs/react-redux#1351 (comment)

[danielkcz]

I guess somebody should actually try it out now when Concurrent is getting finalized. We have some theoretical solution in the next branch which I wanted to release as 2.0 soon, but given that Concurrent is out, it needs to be thoroughly tested.

Although the local state is probably a different beast, I am not sure about specifics either.

[zenVentzi]

I tried reading through some of the discussions on twitter and other github issues but I couldn't make sense of the whole situation.

In layman terms, how should I approach the situation with local store if I intend on using React's Concurrent mode? Some clarity will be much appreciated!

[danielkcz]

I am unsure about Concurrent mode gotchas myself. First of all, we need to try to run current tests in Concurrent mode. It should be possible with RTL custom render. Help appreciated if anyone is willing to give it a try.

[danielkcz]

Just referencing an issue mobxjs/mobx-react-lite#274 that might be worth investigating with Concurrent mode and perhaps add into tests.

[danielkcz]

Since we have deprecated useLocalStore & useAsObservableSource this is probably outdated issue. Closing for now