From f46f31a582947c58655e867cf333b8f72804daa4 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Tue, 23 Aug 2022 15:12:44 +0800
Subject: [PATCH] AI-Chipmunk | 2021.2.1 Patch 2 <debuggerx@debuggerx Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index d2864ca..2d2a84c 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,7 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <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." />
@@ -55,12 +56,11 @@
       <item value="problem tag" />
       <item value="feat: GS-1026 update report." />
       <item value="Submission" />
-      <item value="fix: do not occlude delete button." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="278" />
-        <entry key="ENGLISH" value="279" />
+        <entry key="CHINESE" value="279" />
+        <entry key="ENGLISH" value="280" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>