Part 4 is already on our channel! Learn about MobX integration with @tanstack/react-query -> ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-rNuIyo994OY.html&ab_channel=CodiLime
Thanks for the great talk! That was very helpful We rarely see such advanced content in the field of frontend development Keep going, we really need this kind of talks
I tryed to reproduce this behavior but seens that the context value is persited out of the box, no need for react-ioc. (using react suspense + lazy + toggling component rendering on view)
Here comes part 3 - Advanced DataStore with RxJS. It presents a step-by-step guide to retrieving data from the backend with non-trivial features like cancellation, retrying on error, polling. Check this out: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-lgQXXMhUTgc.html
Thanks for the great talk . i am Angular developer, currently i am investing my time in learning React. This implementation is more likely angular by using provider and injector . i recommend for those specially who come from angular world and want to learn React.👍
thanks for great talk 47:50 I would expect this behavior because you want to clean up the created stores, right? Is the memory also freed or am I wrong?
Thanks for your comment! It depends on the requirements you have. When you need to cache the state between different routes, you should lift this store up to level, but if you want to clear the memory and fetch the data again when the user returns to this page, put it at level.
Amazing, have you heard about React-Query? "Performant and powerful data synchronization for React Fetch, cache and update data in your React and React Native applications all without touching any "global state"."
ReactQuery is powerful solution for fetching data from server side. You can't manage client-state with that. MobX offers you to manage both server and client states in the same way including cached computed/derived state. In the next episode we are going to show how to re-implement ReactQuery behaviors (retrying queries, cancelling) using MobX and RxJS together.
We are happy to use ReactTestingLibrary for unit and integration testing. All we need is to simulate server responses using the MockServiceWorker library, simulate the browser location and LocalStorage if necessary. Then you don't need to provide any mock services or stores through the react-ioc provider. We didn't write any unit test to give a single store a satisfactory code coverage - we only needed an integration tests.
