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.
This is more of a comment than a real request for change. Before I stumbled upon components-flutter, I implemented a similar set of widgets for our flutter app (though not as flexible). I used Riverpod for state management. On its website it says, that it is meant to be the successor of the provider package used in this repo. It was written by the same author(s?).
Describe the solution you'd like
Given that 1.0 is out already it might be too late, but would you consider switching provider for riverpod? Some advantages:
listening to changes without redrawing the widget (e.g. listen to microphone/camera mute state and store it in local storage for persistence)
listening to changes outsite the widget tree (in our case to communicate with global services injected by injectable)
easily combine providers (allows splitting up providers in smaller chunks)
Hi, I am trying to read Riverpod docs. Since components should not have too many users at present, if Riverpod can simplify the amount of code and improve performance, I can try to migrate without changing too much code structure.
thanks for your response and for considering riverpod.
However, after trying to switch to these components in our app, I realized that it's really hard to customize e.g. the device buttons without reimplementing the whole hierarchy of widgets to actually use the customized version. This is not a problem with this repo, but with how flutter works IMHO. I'll stay with our current widget implementations for now
Feel free to close this issue unless you want to have it around if you plan to switch to riverpod at some point 😄
Is your feature request related to a problem? Please describe.
This is more of a comment than a real request for change. Before I stumbled upon
components-flutter
, I implemented a similar set of widgets for our flutter app (though not as flexible). I used Riverpod for state management. On its website it says, that it is meant to be the successor of the provider package used in this repo. It was written by the same author(s?).Describe the solution you'd like
Given that 1.0 is out already it might be too late, but would you consider switching provider for riverpod? Some advantages:
Describe alternatives you've considered
I'll stick to riverpod for our app as both riverpod and provider can coexist to allow for incremental transitioning
Additional context
Thanks for this awesome library/ecosystem and for keeping improving it 🚀 🙏
The text was updated successfully, but these errors were encountered: