A few questions regarding your library #21
-
Maybe it would make sense to create a Discussion section and move this issue there. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Feel free to ask any other question if you still have doubts |
Beta Was this translation helpful? Give feedback.
-
Thanks for thoroughly answering each single point! One of the things that bugged me in Riverpod was not being able to immediately invoke the function inside a provider, but having to create a I really like this signals concept and the fact your library — by not using global state — leverages the Flutter widget tree. Also, the examples and the documentation are immensely helpful. Really appreciate your effort! Well done! 🎊 |
Beta Was this translation helpful? Give feedback.
Solid
widget to pass signals down to the treeriverpod
2.1. Internally it's very similar to a
ValueNotifier
but with more extra built-in features (likepreviousValue
,select
, customizablecomparator
and so on)2.2. When using the
Solid
widget, every signal or provider you declare is lazy by default (but you can customise the behaviour for providers). They will be created only when read. TheResource
is always lazy, it runs only when used inside aResourceBuilder
or when you callresolve()
yourself. If you usecreateSignal
outside of theSolid
widget it gets created immediately.2.3. I …