Depending on context doesn't trigger rebuild/changes? about scoped_model HOT 3 CLOSED

Hmmm so thats how it is. Shouldn't this be in the docs. Anyways I prefer this approach even though it might not be the more performant one. Thanks.

from scoped_model.

Yep, that's expected. You need to pass through rebuildOnChange: true as part of your call to ScopedModel.of, or it will only grab the value the first time. I'm considering adding a listen or on method instead to make this a bit clearer.

E.g. you need to change this:

static TestModel of(BuildContext context) => ScopedModel.of<TestModel>(context);

to this:

static TestModel of(BuildContext context) =>
      ScopedModel.of<TestModel>(context, rebuildOnChange: true);

from scoped_model.

@brianegan I was stuck on a really weird problem related to this.

I have a complicated model which has a big map of data. I was using this way of doing things

    final linesModel =
        ScopedModel.of<LinesModel>(context, rebuildOnChange: false);
    final authUserModel =
        ScopedModel.of<AuthUserModel>(context, rebuildOnChange: false);
    final presenceModel =
        ScopedModel.of<PresenceModel>(context, rebuildOnChange: true);

However, I was using the above outside of the build method and in a lifecycle method, and I have one of the rebuildOnChange set to true for presenceModel. Children of widgets in the build method changed something in the presenceModel and so the build method re-mounted.
So the observation is that even if you use this direct access way in a lifecycle method instead of descendent, and you put rebuildOnChange/listen as true, it causes the build method to run again and hence calling the initState of all children widget again.

However, my weird problem was that this caused an infinite loop in android but not on web. I was stuck on it for hours and can't figure out why on android, children widgets would keep remounting/their initstate kept getting called in an infinite loop as they were updating presenceModel data. I had to change the rebuildOnChange to false for android to stop the loop. However, in flutter run web/chrome, the infinite loop never happened.

Am I missing something fundamental about flutter? Or something fundamental about platforms? Or something fundamental about scoped_model specifically as it relates to web vs. android?

Please help, I'm really stuck on why flutter is inconsistent on both platforms. I chose flutter because I thought it would be super consistent.

from scoped_model.