How should you call the data classes in your app?
You could, in theory, set up a place in static memory where all your data classes will reside, but that won't play well with tools such as Hot Reload and could even introduce some undefined behavior down the road. The better options involve placing your data classes in the widget tree so they can take advantage of your application's life cycle.
The question then becomes, how can you place a model in the widget tree? Models are not widgets, after all, and there is nothing to build onto the screen.
A possible solution is using InheritedWidget. So far, we've only been using two types of widgets: StatelessWidget and StatefulWidget. Both of these widgets are concerned with rendering widgets onto the screen; the only difference is that one can change and the other cannot. InheritedWidget is another beast entirely. Its job is to pass data down to its children,...
