Problem is in the import statements. You have not used curly braces while importing some components like createHistory. If a component uses a default export like: export default X Then you can simply import it like: import X from ‘./X’; But if you are using a named export like: export const X=1; Then you need … Read more
If none of the other solutions worked for you, you can try this in your jest “moduleNameMapper”: { “^lodash-es$”: “lodash” } It will replace lodash-es with the commonjs version during testing runtime.
So after reading through some related answers (specifically this one and this one and looking at @basarat’s answer to the question, I managed to find something that works for me. It looks (to my relatively new React eyes) like Connect was not supplying an explicit interface to the container component, so it was confused by … Read more
In redux-saga, the equivalent of the above example would be export function* loginSaga() { while(true) { const { user, pass } = yield take(LOGIN_REQUEST) try { let { data } = yield call(request.post, ‘/login’, { user, pass }); yield fork(loadUserData, data.uid); yield put({ type: LOGIN_SUCCESS, data }); } catch(error) { yield put({ type: LOGIN_ERROR, error … Read more
Normal re renders are normal in RN. That is just RN updating the react tree and updating views. If you dont have a performance issue then you can ignore this. Otherwise, please explain the problem because the console log is fine. Render item executes for EACH item in the data array you pass to FlatList. … Read more
connect state on your Child components Using connect on child components has the following advantages: Your parent component need not bother about connecting all the props required by its children even though the parent itself is not using the prop. Child components become more reusable, and easily maintainable. Avoids passing down props blindly from parent … Read more
The signature for the function passed to wrapper.getServerSideProps has changed in next-redux-wrapper v7.x. Replace the following. export const getServerSideProps = wrapper.getServerSideProps(async ({req, store}) => { // Code here }) With the right signature. export const getServerSideProps = wrapper.getServerSideProps((store) => async ({ req }) => { // Code here })
Redux docs recommends you to use the spread operator approach instead of the Object.assign As per the docs: An alternative approach is to use the object spread syntax proposed for the next versions of JavaScript which lets you use the spread (…) operator to copy enumerable properties from one object to another in a more … Read more
Instead of using BrowserRouter you could use the Router with custom history like import { Router } from ‘react-router’ import createBrowserHistory from ‘history/createBrowserHistory’ export const history = createBrowserHistory() <Router history={history}> <App/> </Router> in which case your history.push() will work. With BrowserRouter history.push doesn’t work because Creating a new browserHistory won’t work because <BrowserRouter> creates its … Read more
No, you should not store function references in the redux store. They are not serializable, and as you mentioned state should be serializable at all times. The most redux-friendly approach I can think of is just to keep the map of hotkeys to their actionCreatorFuncNames.