[stacked] What is the point of onModelReady? about stacked

[FilledStacks]

@creativecreatorormaybenot the point of it is to run logic when the model has been constructed, in a readable manner. You'll find most of my decisions will be verbose to make it clear what's happening when reading the code. Not because of a technical requirement.

[creativecreatorormaybenot]

@FilledStacks I see. No worries then because I can still use the other way if I prefer it 👍

[melis-m]

This might not be directly related to stacked, but what's the point of having a ViewModel.init() function that you call from onModelReady. Couldn't you achieve the same result by directly putting the content of init inside the ViewModel's constructor ?

[FilledStacks]

@melis-m construction is blocking. It's the same for some things. But if you want to for instance fetch and set data it would be good not to do it in the constructor.

[melis-m]

@FilledStacks but init is blocking as well, and it's not as if there's actually any really blocking stuff, like even making an http request is only just launching a future.
I just don't really understand the point of splitting the construction and the initialization part :\