question: idiomatic way to reference dispatcher and/or state?
See original GitHub issuehi andrew,
redux-thunk facilitates referencing dispatcher and state by automatically providing the dispatcher
and getState
methods.
how would you recommend gaining similar references using redux-promise?
regards, tony
Issue Analytics
- State:
- Created 8 years ago
- Comments:12
Top Results From Across the Web
Untitled
R b rap love songs, Ils reference datum, Blackberry 9300 white price, ... Concept 2 rower model c assembly, How to write a...
Read more >Untitled
Long way home 1997, Ganga telugu serial zee telugu, 29 000 mercedes. ... Amministratore stefano giannangeli, Map tile sets, Vidal art reference, ...
Read more >Untitled - Snap!
Instead this block reports how many milliseconds it took to perform the ... ,online,system,better,three,never,always,love,say,might,next,company,state ...
Read more >Untitled
Mac sense of style eyeliner, Motorbikes love quotes, Evolva 1-2-3 plus zebra, ... Cpa exam practice questions free, Noticias economicas 3 de febrero...
Read more >ED262590.pdf - ERIC
Barbara Kryk (Poznan): How do proper names refer? ... St lvo Ohlandor. 1976. ... The question that we may raise now is whether...
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 FreeTop 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
Top GitHub Comments
@kevana, i just tried the strategy outlined above, and the behavior i witnessed was the thunk not being executed.
the following doesn’t take i think because
createAction
puts the ‘thunk’ in apayload
field…?i have however had some luck with something like:
I am not sure what you mean. I have a “client action creator” that can dispatch success/error depending on the outcome of the api call. I use it in many other actions so I am no really repeating that code.