You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm always frustrated with this Stream Feeds when I modified the code from single provider to multiproviders. After inspecting the widget, I found the widget wasn't posittioned properly. I am trying to find a way.
Is there any some example for multiprovider with your stream activity feeds product? I think no need for full code, just main.dart file is enough. (provider is normally set in Materialapps part.)
Describe the solution you'd like
I wonder if feedprovider can go into Multiprovider braket rather than staying in the builder constructor.
Describe alternatives you've considered
if not, can we not assert Feedprovider on the Materialapp level? if possible how we can add Feedprovider on the subpage without asserting FeedProvider on the builder constructor of Materialapp?
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm always frustrated with this Stream Feeds when I modified the code from single provider to multiproviders. After inspecting the widget, I found the widget wasn't posittioned properly. I am trying to find a way.
Is there any some example for multiprovider with your stream activity feeds product? I think no need for full code, just main.dart file is enough. (provider is normally set in Materialapps part.)
Describe the solution you'd like
I wonder if feedprovider can go into Multiprovider braket rather than staying in the builder constructor.
Describe alternatives you've considered
if not, can we not assert Feedprovider on the Materialapp level? if possible how we can add Feedprovider on the subpage without asserting FeedProvider on the builder constructor of Materialapp?
Additional context
The text was updated successfully, but these errors were encountered: