From eb25dfe1adf3160136aed74389711e275dc70e3e Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Tue, 23 Aug 2022 13:53:48 +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 0a7e150..937896c 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="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." />
       <item value="Finds [Semantics] widgets matching the given `label`, either by [RegExp.hasMatch] or string equality. The framework may combine semantics labels in certain scenarios, such as when multiple [Text] widgets are in a [MaterialButton] widget. In such a case, it may be preferable to match by regular expression. Consumers of this API __must not__ introduce unsuitable content into the semantics tree for the purposes of testing; in particular, you should prefer matching by regular expression rather than by string if the framework has combined your semantics, and not try to force the framework to break up the semantics nodes. Breaking up the nodes would have an undesirable effect on screen readers and other accessibility services. Sample code ```dart expect(find.bySemanticsLabel('Back'), findsOneWidget); ``` If the `skipOffstage` argument is true (the default), then this skips nodes that are [Offstage] or that are from inactive [Route]s." />
       <item value="Cached &amp; lazily loaded instance of [FirebasePlatform]. Avoids a [MethodChannelFirebase] being initialized until the user starts using Firebase. The property is visible for testing to allow tests to set a mock instance directly as a static property since the class is not initialized." />
@@ -55,12 +56,11 @@
       <item value="Submission" />
       <item value="fix: do not occlude delete button." />
       <item value="遮挡" />
-      <item value="ratio" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="275" />
-        <entry key="ENGLISH" value="276" />
+        <entry key="CHINESE" value="276" />
+        <entry key="ENGLISH" value="277" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>