Hey everyone, I hope you are doing good. I would like to share with you a new framework that I have been working on in the last couple of months. It’s called Caesura and it’s powered by ReSwift.
Please, visit the repository for more information and I strongly recommend you to try the example project to see what the framework is capable of.
Any suggestion is more than welcome, as well as your star ;)
Hey guys, it's me again :) Hope you are doing well. I've been using ReSwift for a year now and there is always some concern in my mind: is it really a good practice to keep all the states/substates in the memory?
Say I have a view, which dispatches an action to its middleware, the middleware talks to the network service and fetches the data back, after that it fires an action to set the data to its viewState, then the view observed its state changes and reflects that. Everything works perfect. But if I keep doing this for each modules in my app, will it keep increasing the memory usage and some day it might be too high?
I would like to know what are the todos and not-todos when dealing with various modules with various data (info displayed/stored in the state).
LoadInitialStateActionthat resolves with an array of
[Item]; i have a middleware
guarding for that action, and if it is
someThunkbeing the next asynchronous action that relies on
items. what i'm running into is the
ReSwift:ConcurrentMutationStateError- Action has been dispatched while a previous action is being processedoccurring when my
storeand using a serial
dispatch, but that didnt work :worried: my fix was basically
DispatchQueue.main.asyncAfter(.now() + 1)https://twitter.com/ios_memes/status/1159781903559528450/photo/1