Your reducer must be pure. Currently it is not pure. It calls deal() which calls getRandom() which relies on Math.random() and thus is not pure. This kind of logic (“generating data”, whether randomized or from user input) should be in the action creator. Action creators don’t need to be pure, and can safely use Math.random(). … Read more
This happens because you’re re-defining renderField as a new component every time you render which means it looks like a new component to React so it’ll unmount the original one and re-mounts the new one. You’ll need to hoist it up: const renderField = ({ input, label, type, meta: { touched, invalid, error } }) … Read more
Possibly it’s not actual and the question is outdated, but there is thunkAPI as second parameter in payload creator of createAsyncThunk, so it can be used like so export const updateData = createAsyncThunk(‘data/update’, async (params, {dispatch}) => { const result = await sdkClient.update({ params }) dispatch(getData()) return result })
The createAsyncThunk can have the types defined on the generics: export const unsubscribeMeta = createAsyncThunk<apiUnsubscribeResponse, void, {state: RootState }>( ‘meta/unsubscribe’, async (_, { getState }) => { const { meta } = getState(); const res = await client.post<apiUnsubscribeResponse>( `/meta/unsubscribe/${meta.subscriptionId}` ); return res.data.data; } ); Defining the state will automatically make the getState be aware of … Read more
To be able to understand how Provider and connect work we need to understand 2 concepts in React 1- Context api: Context is a way to pass data through the component tree without having to pass the props down manually at every level, you can learn more about context here 2- Higher Order Component (HOC): … Read more
IMO, the right place to sort data is not directly in the reducers but in the selectors. From redux docs: Computing Derived Data Reselect is a simple library for creating memoized, composable selector functions. Reselect selectors can be used to efficiently compute derived data from the Redux store. I’m currently using selectors to filter and … Read more
Dispatch initiates new action and it’s go through full chain of middlewares. Next – send current action into next middleware in chain.
One possible solution, as you already mentioned, is to use channels. Here is an example that should work in your case: import { channel } from ‘redux-saga’ import { put, take } from ‘redux-saga/effects’ const downloadFileChannel = channel() export function* loadFile(id) { … const download = RNFS.downloadFile({ … // push `S_PROGRESS` action into channel on … Read more
Though @Martin Kadlec’s solid answers covers the question, I want to elaborate a bit more on the details and differences on takeEvery and takeLatest and when they might be used so you can derive the possible use-cases of them. TLDR: You can use takeEvery when the returns of all previous tasks are needed. For example … Read more