<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}"/>
<itemvalue="{@template riverpod.refresh} Forces a provider to re-evaluate its state immediately, and return the created value. Writing: ```dart final newValue = ref.refresh(provider); ``` is strictly identical to doing: ```dart ref.invalidate(provider); final newValue = ref.read(provider); ```"/>
<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. 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="failed"/>
<itemvalue="success"/>
<itemvalue="loading"/>
@ -67,11 +72,6 @@
<itemvalue="> The value returned by this getter implicitly converts floating-point > component values (such as `0.5`) into their 8-bit equivalent by using > the [toARGB32] method; the returned value is not guaranteed to be stable > across different platforms or executions due to the complexity of > floating-point math."/>
<itemvalue="opacity"/>
<itemvalue="The value of the 'assets' field is expected to be a list of relative file paths. Try converting the value to be a list of relative file paths."/>
<itemvalue="The [exitType] indicates what kind of exit to perform. For [ui.AppExitType.cancelable] exits, the application is queried through a call to [handleRequestAppExit], where the application can optionally cancel the request for exit. If the [exitType] is [ui.AppExitType.required], then the application exits immediately without querying the application."/>
<itemvalue="This differs from calling `dart:io`'s [exit] function in that it gives the engine a chance to clean up resources so that it doesn't crash on exit, so calling this is always preferred over calling [exit]. It also optionally gives handlers of [handleRequestAppExit] a chance to cancel the application exit."/>
<itemvalue="Exits the application by calling the native application API method for exiting an application cleanly. This differs from calling `dart:io`'s [exit] function in that it gives the engine a chance to clean up resources so that it doesn't crash on exit, so calling this is always preferred over calling [exit]. It also optionally gives handlers of [handleRequestAppExit] a chance to cancel the application exit."/>
<itemvalue="To listen for changes in the application lifecycle state, define an [onStateChange] callback. See the [AppLifecycleState] enum for details on the various states."/>
<itemvalue="To listen for requests for the application to exit, and to decide whether or not the application should exit when requested, create an [AppLifecycleListener] and set the [onExitRequested] callback."/>