You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @ctrlplusb! Firstly, thanks as always for putting out these super useful libraries.
For my usecase, I am using it with Redux and a common usecase for that is to to check if the data in question is already in the store or not. To do that, one needs access to the store, which currently is not passed on by withJob to work.
For my own work, I just manually added that to the context, and passed it through but what are your thoughts on a more standard solution for such cases? I know you've previously talked about an abstraction like redux-jobs but I imagine that too would need this piece of information.
Thoughts?
The text was updated successfully, but these errors were encountered:
I would have imagined a wrapper component of sorts. I'll have to spike out an example on codesandbox.io. But it would be great to be able to leave react-jobs as is and simply compose over it.
Hi @ctrlplusb! Firstly, thanks as always for putting out these super useful libraries.
For my usecase, I am using it with Redux and a common usecase for that is to to check if the data in question is already in the store or not. To do that, one needs access to the store, which currently is not passed on by
withJob
towork
.For my own work, I just manually added that to the context, and passed it through but what are your thoughts on a more standard solution for such cases? I know you've previously talked about an abstraction like
redux-jobs
but I imagine that too would need this piece of information.Thoughts?
The text was updated successfully, but these errors were encountered: