From 3cdbed6af987ec23bd512a042d9c3f6aa1176017 Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Mon, 27 Oct 2025 21:08:47 +0800
Subject: [PATCH] AI-Narwhal 4 Feature Drop | 2025.1.4 <debuggerx@debuggerx-PC
 Update yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 27e0519..5792248 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -22,6 +22,11 @@
     <option name="translationDialogLocationY" value="567" />
     <option name="translationDialogWidth" value="1381" />
     <histories>
+      <item value="- [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 &quot;hard refresh&quot;." />
+      <item value="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." />
+      <item value="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 &quot;pull to refresh&quot; or &quot;retry on error&quot;, to restart a specific provider. {@endtemplate}" />
+      <item value="{@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); ```" />
+      <item value="{@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." />
       <item value="failed" />
       <item value="success" />
       <item value="loading" />
@@ -67,11 +72,6 @@
       <item value="&gt; The value returned by this getter implicitly converts floating-point &gt; component values (such as `0.5`) into their 8-bit equivalent by using &gt; the [toARGB32] method; the returned value is not guaranteed to be stable &gt; across different platforms or executions due to the complexity of &gt; floating-point math." />
       <item value="opacity" />
       <item value="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." />
-      <item value="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." />
-      <item value="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." />
-      <item value="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." />
-      <item value="To listen for changes in the application lifecycle state, define an [onStateChange] callback. See the [AppLifecycleState] enum for details on the various states." />
-      <item value="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." />
     </histories>
     <option name="languageScores">
       <map>