___actions
this store our actions and action creators
___reducers
define our user reducer (state) type and create an initial state for it
___selectors
cache the state for us and we’ll recalculate only the parts of the state that have changed
___sagas
Sagas’ll handle our logic and it’ll allow us to keep actions, At the bottom of sagas, there is a watcher saga watchGetUserStart(), which waits for the GET_USER_START action to be called (this action is usually called from some component or from different saga)
The takeLatest saga effect will cancel the previous saga task (in our example handleGetUserStart) and start a new one—if the same action has been called multiple times.
Rencently I work with redux-saga,in my opinion, it is a middleware used handle async request and redux state.There are key component and comprehension of redux-saga.
If you want output some log in react component, you can do like this:
return (
<MapWithMarker
googleMapURL={(console.log(googleMapApiUrl),googleMapApiUrl)}
loadingElement={<div style={{ height: '100%' }} />}
containerElement={<div style={{ height: '400px' }} />}
mapElement={<div style={{ height: '100%' }} />}
/>
);