<itemvalue="Invalidates the state of the provider, causing it to refresh. The refresh is not immediate and is instead delayed to the next read or next frame. Calling [invalidateSelf] multiple times will refresh the provider only once. Calling [invalidateSelf] will cause the provider to be disposed immediately."/>
<itemvalue="{@template riverpod.invalidate} Invalidates the state of the provider, destroying the state immediately and causing the provider to rebuild at some point in the future."/>
<itemvalue="Forces a provider to re-evaluate its state immediately, and return the created value."/>
<itemvalue="If you do not care about the return value of [refresh], use [invalidate] instead. Doing so has the benefit of: - making the invalidation logic more resilient by avoiding multiple refreshes at once. - possibly avoids recomputing a provider if it isn't needed immediately. This method is useful for features like "pull to refresh" or "retry on error", to restart a specific provider. {@endtemplate}"/>
<itemvalue="force supply stop"/>
<itemvalue="force supply estop"/>
<itemvalue="Raw RGBA format. Unencoded bytes, in RGBA row-primary form with premultiplied alpha, 8 bits per channel."/>
@ -58,16 +62,12 @@
<itemvalue="diameter ratio"/>
<itemvalue="physics"/>
<itemvalue="controller"/>
<itemvalue="A delegate that supplies children for [ListWheelScrollView] using a builder callback. [ListWheelScrollView] lazily constructs its children to avoid creating more children than are visible through the [Viewport]. This delegate provides children using an [IndexedWidgetBuilder] callback, so that the children do not have to be built until they are displayed."/>
<itemvalue="list wheel child builder delegate"/>
<itemvalue="list wheel child looping list delegate"/>
debuggerx
5 months ago