Context-aware provider initialisation in Flutter
I’m using the following way to init each provider when needed and dispose them. Currently i’m running into an issue where I can’t access the same provider instance if I move to another screen.
A multiple single source of truth problem
I was recently studying state management (flutter provider), and in every example I saw it was necessary to create a single source of truth so that the data could be read and updated in the application. However, in an authorial application of mine I came across the need to dynamically create several instances of a controller class.