From f61dd6f5ec13d9e2c60abdcb82ad47ef644b908c Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Tue, 13 Sep 2022 14:11:31 +0800
Subject: [PATCH] AI-Chipmunk | 2021.2.1 Patch 2 <debuggerx@debuggerx 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 a6b4617..45f6518 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,9 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="add missing params of group chat item." />
+      <item value="add missing params when create group chat item." />
+      <item value="add leak params when create group chat item." />
       <item value="Controls a WebView, such as an [InAppWebView] widget instance, a [HeadlessInAppWebView] instance or [InAppBrowser] WebView instance. If you are using the [InAppWebView] widget, an [InAppWebViewController] instance can be obtained by setting the [InAppWebView.onWebViewCreated] callback. Instead, if you are using an [InAppBrowser] instance, you can get it through the [InAppBrowser.webViewController] attribute." />
       <item value="A scrolling container that animates items when they are inserted or removed. This widget's [AnimatedListState] can be used to dynamically insert or remove items. To refer to the [AnimatedListState] either provide a [GlobalKey] or use the static [of] method from an item's input callback. This widget is similar to one created by [ListView.builder]. {@youtube 560 315 https:www.youtube.comwatch?v=ZtfItHwFlZ8} {@tool dartpad} This sample application uses an [AnimatedList] to create an effect when items are removed or added to the list. See code in examplesapilibwidgetsanimated_listanimated_list.0.dart {@end-tool} See also: [SliverAnimatedList], a sliver that animates items when they are inserted or removed from a list." />
       <item value="{@template flutter.widgets.animatedList.initialItemCount} The number of items the list will start with. The appearance of the initial items is not animated. They are created, as needed, by [itemBuilder] with an animation parameter of [kAlwaysCompleteAnimation]. {@endtemplate}" />
@@ -53,14 +56,11 @@
       <item value="Warning: A call to tap() with finder &quot;exactly one widget with text &quot;Delete&quot; (ignoring offstage widgets): Text(&quot;Delete&quot;, inherit: true, family: Montserrat_600, familyFallback: [Montserrat], size: 18.0, weight: 600, letterSpacing: -0.2, height: 1.2x, dependencies: [MediaQuery, DefaultTextStyle])&quot; derived an Offset (Offset(98.0, 1028.0)) that would not hit test on the specified widget. Maybe the widget is actually off-screen, or another widget is obscuring it, or the widget cannot receive pointer events. Indeed, Offset(98.0, 1028.0) is outside the bounds of the root of the render tree, Size(375.0, 812.0). The finder corresponds to this RenderBox: RenderParagraphcc8a4 relayoutBoundary=up20 The hit test result at that offset is: HitTestResult(HitTestEntryc7125(RenderView6eff7), HitTestEntryeb0ec(&lt;AutomatedTestWidgetsFlutterBinding&gt;))" />
       <item value="The overflowing RenderFlex has an orientation of Axis.horizontal. The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex. Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size. This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView." />
       <item value="Warning: A call to tap() with finder &quot;exactly one widget with text &quot;Delete&quot; (ignoring offstage widgets): Text(&quot;Delete&quot;, inherit: true, family: Montserrat_600, familyFallback: [Montserrat], size: 38.4, weight: 600, letterSpacing: -0.2, height: 1.2x, dependencies: [MediaQuery, DefaultTextStyle])&quot; derived an Offset (Offset(209.6, 1060.8)) that would not hit test on the specified widget. Maybe the widget is actually off-screen, or another widget is obscuring it, or the widget cannot receive pointer events. Indeed, Offset(209.6, 1060.8) is outside the bounds of the root of the render tree, Size(800.0, 600.0)." />
-      <item value="Warning: At least one test in this suite creates an HttpClient. When running a test suite that uses TestWidgetsFlutterBinding, all HTTP requests will return status code 400, and no network request will actually be made. Any test expecting a real network connection and status code will fail. To test code that needs an HttpClient, provide your own HttpClient implementation to the code under test, so that your test can consistently provide a testable response to the code under test." />
-      <item value="create Main User Record" />
-      <item value="A mixin class for providing string and [DiagnosticsNode] debug representations describing the properties of an object. The string debug representation is generated from the intermediate [DiagnosticsNode] representation. The [DiagnosticsNode] representation is also used by debugging tools displaying interactive trees of objects and properties. See also: [debugFillProperties], which lists best practices for specifying the properties of a [DiagnosticsNode]. The most common use case is to override [debugFillProperties] defining custom properties for a subclass of [DiagnosticableTreeMixin] using the existing [DiagnosticsProperty] subclasses. [DiagnosticableTree], which extends this class to also describe the children of a tree structured object. [DiagnosticableTree.debugDescribeChildren], which lists best practices for describing the children of a [DiagnosticsNode]. Typically the base class already describes the children of a node properly or a node has no children. [DiagnosticsProperty], which should be used to create leaf diagnostic nodes without properties or children. There are many [DiagnosticsProperty] subclasses to handle common use cases." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="330" />
-        <entry key="ENGLISH" value="331" />
+        <entry key="CHINESE" value="333" />
+        <entry key="ENGLISH" value="334" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>