To introduce a good architecture you need to separate your State from Business Logic
Good example but I wish I could see that in a code example. Something like changeNotifier class which has all the state code and business logic together and then seprating them step by step.
That's a good suggestion.
I was thinking of doing that, but to do that I have to build a real example the wrong way, then make a refactoring tutorial about it.
It would definitely be helpful, maybe in the future I'll find a way to do that and document it.
Good example but I wish I could see that in a code example. Something like changeNotifier class which has all the state code and business logic together and then seprating them step by step.
That's a good suggestion.
I was thinking of doing that, but to do that I have to build a real example the wrong way, then make a refactoring tutorial about it.
It would definitely be helpful, maybe in the future I'll find a way to do that and document it.