According to this page: you are doing the correct thing including history in your thunk input.

Quote: "The solution here is simply to include the history object (provided to all route components) in the payload of the action, and your async handler can use this to navigate when appropriate."

Related Query

More Query from same tag