Will it be exposed ReactReduxContext from react-redux?

[budarin]

will there be a new syntax of context available for using in my HOCs or should I using connect for accesing store and reinventing another one context?

[markerikson]

You'll still be using connect() as normal - any changes to use the new context API will be an internal implementation detail. See #898 for an idea of what it may look like.

[budarin]

@markerikson
I need to have access to store\s methods and properties not data
connect provide me with state but I need its properties & methods

it would be safe to share ReactReduxContext.Consumer for such demands

[markerikson]

What's your use case? Why do you need access to the store itself elsewhere in the component tree?

[budarin]

@markerikson
our bank app had a huge state so we have to dynamic add/remove reducers and sagas for app sections
at now we are using HOC with store context for these purposes
without access to the store object it's impossible

[budarin]

@markerikson
any suggestion?

we really need access to store.replaceReducer
should we reinvent new store context to have access to?

[timdorr]

@budarin No changes have been made or will be made in the near future. We have no idea how things will actually shake out.

[budarin]

so we have to make an additional context that will duplicate the existing redux internal context - it's overhead

[budarin]

@timdorr
@markerikson

at now we have this ugly code

return (
        <Provider store={store}>
            <StoreContextProvider store={store}>
                   .....
            </StoreContextProvider>
        </Provider>
    );

[timdorr]

The store is made available to your connected components. You don't need to add your own context.

[budarin]

@timdorr
in new versions of React with new Context API connected components will be able to get state of a store and dispatch method only, but we need an access to the the store to have ability to execute

store.replaceReducer(...) 

[jwugit]

Hi, im having similar issue trying to make redux code split reducers.

@budarin
did you ever found a solution to this issue ?

@timdorr @markerikson
Now that the new react context api is updated,
is there any consideration to support exposure to the store from connect or at least exposure to let use or call redux store replaceReducer ?

[markerikson]

Our current WIP v6 PRs at #995 and #1000 both actually put both the store and the store state into context. I don't think we're going to officially support accessing it, but I don't want to intentionally block people from accessing it either.

Beyond that, please try out the PRs and give us feedback on how well they work (or don't work)!

[budarin]

@jwugit I've found on the internet a snippet from Dan Abramov but I lost the link
try to find it

[jwugit]

@markerikson
Ok thanks, i will give them a try tomorrow and see if it works out.

@budarin
I did found and looked up a lot of snippets,
This is not actually an issue if there is only one store in the app.
It can be imported from the store.js file again, since is a singleton, in any component to access the replaceReducer function.

But my specific uses case is having multiple store and i cannot use the singleton approach since i wouldnt be able to target the correct store instance.

@markerikson @budarin
if you want to know about my use case, i wrote up a question here.
https://stackoverflow.com/questions/52957552/how-to-replace-old-react-contexttypes-with-new-react-context-api-when-using-dyna

Initially i thought this would be a react problem since it is changing the legacy context to new context api. But Dan mention it's more of a react-redux decision of letting context be exposed or not in the upcoming updates. So here i am 😃 .
https://twitter.com/dan_abramov/status/1055445608104890368