<itemvalue="If non-null, the style to use for this text. If the style's "inherit" property is true, the style will be merged with the closest enclosing [DefaultTextStyle]. Otherwise, the style will replace the closest enclosing [DefaultTextStyle]."/>
<itemvalue="Instantiating non-const instances of this class in your app will mean the app cannot be built in release mode with icon tree-shaking (it need to be explicitly opted out at build time). See [staticIconProvider] for more context."/>
<itemvalue="Instantiating non-const instances of this class in your app will mean the app cannot be built in release mode with icon tree-shaking (it need to be explicitly opted out at build time). See [staticIconProvider] for more context."/>
<itemvalue="A description of an icon fulfilled by a font glyph. See [Icons] for a number of predefined icons available for material design applications. In release builds, the Flutter tool will tree shake out of bundled fonts the code points (or instances of [IconData]) which are not referenced from Dart app code. See the [staticIconProvider] annotation for more details."/>
<itemvalue="A description of an icon fulfilled by a font glyph. See [Icons] for a number of predefined icons available for material design applications. In release builds, the Flutter tool will tree shake out of bundled fonts the code points (or instances of [IconData]) which are not referenced from Dart app code. See the [staticIconProvider] annotation for more details."/>
<itemvalue="When looking to easily toggle the default decorations, you can use [ScrollBehavior.copyWith] instead of creating your own [ScrollBehavior] class. The `scrollbar` and `overscrollIndicator` flags can turn these decorations off. {@endtemplate}"/>
<itemvalue="When looking to easily toggle the default decorations, you can use [ScrollBehavior.copyWith] instead of creating your own [ScrollBehavior] class. The `scrollbar` and `overscrollIndicator` flags can turn these decorations off. {@endtemplate}"/>
@ -70,8 +72,6 @@
<itemvalue="The list of providers that this provider potentially depends on. This list must contains the classesfunctions annotated with `@riverpod`, not the generated providers themselves. Specifying this list is strictly equivalent to saying "This provider may be scoped". If a provider is scoped, it should specify [dependencies]. If it is never scoped, it should not specify [dependencies]."/>
<itemvalue="The list of providers that this provider potentially depends on. This list must contains the classesfunctions annotated with `@riverpod`, not the generated providers themselves. Specifying this list is strictly equivalent to saying "This provider may be scoped". If a provider is scoped, it should specify [dependencies]. If it is never scoped, it should not specify [dependencies]."/>
<itemvalue="} {@template riverpod.listen} Listen to a provider and call [listener] whenever its value changes. Listeners will automatically be removed when the provider rebuilds (such as when a provider listened with [Ref.watch] changes). Returns an object that allows cancelling the subscription early."/>
<itemvalue="} {@template riverpod.listen} Listen to a provider and call [listener] whenever its value changes. Listeners will automatically be removed when the provider rebuilds (such as when a provider listened with [Ref.watch] changes). Returns an object that allows cancelling the subscription early."/>
<itemvalue="- [asReload] (false by default) can be optionally passed to tell Riverpod to clear the state before refreshing it. This is only useful for asynchronous providers, as by default, [AsyncValue] keeps a reference on state during loading states. Using [asReload] will disable this behavior and count as a "hard refresh"."/>
<itemvalue="- [asReload] (false by default) can be optionally passed to tell Riverpod to clear the state before refreshing it. This is only useful for asynchronous providers, as by default, [AsyncValue] keeps a reference on state during loading states. Using [asReload] will disable this behavior and count as a "hard refresh"."/>
<itemvalue="As opposed to [refresh], the rebuild is not immediate and is instead delayed by an undefined amount of time. Typically, the rebuild happens at the next tick of the event loop. But if a provider is not listened to, the rebuild may be delayed until the provider is listened to again."/>
<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}"/>
debuggerx
1 month ago