diff --git a/debugger.xml b/debugger.xml
index 4b14fa9..8490f60 100644
--- a/debugger.xml
+++ b/debugger.xml
@@ -113,13 +113,10 @@
   </component>
   <component name="XDebuggerSettings">
     <data-views />
-    <general />
+    <general>
+      <evaluation-dialog-mode>CODE_FRAGMENT</evaluation-dialog-mode>
+    </general>
     <debuggers>
-      <debugger id="kotlin_debugger">
-        <configuration>
-          <option name="filterForStdlibAlreadyAdded" value="true" />
-        </configuration>
-      </debugger>
       <debugger id="ObjectiveC">
         <configuration>
           <option name="VALUES_FILTER_ENABLED" value="false" />
diff --git a/pluginAdvertiser.xml b/pluginAdvertiser.xml
index 8ee7513..fc0da05 100644
--- a/pluginAdvertiser.xml
+++ b/pluginAdvertiser.xml
@@ -540,9 +540,8 @@
         <entry key="*.ignore">
           <value>
             <plugin>
-              <option name="myPluginId" value="com.intellij" />
-              <option name="myPluginName" value="IDEA CORE" />
-              <option name="myBundled" value="true" />
+              <option name="myPluginId" value="mobi.hsz.idea.gitignore" />
+              <option name="myPluginName" value=".ignore" />
             </plugin>
           </value>
         </entry>
diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index acd82c3..5da2131 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -5,6 +5,11 @@
     <option name="newTranslationDialogX" value="948" />
     <option name="newTranslationDialogY" value="618" />
     <histories>
+      <item value="Return the presentation of this type as it should appear when presented to users in contexts such as error messages. If [withNullability] is `true`, then [NullabilitySuffix.question] and [NullabilitySuffix.star] will be be represented as `?` and ``. [NullabilitySuffix.none] does not have any explicit presentation. If [withNullability] is `false`, nullability suffixes will not be included into the presentation. Clients should not depend on the content of the returned value as it will be changed if doing so would improve the UX." />
+      <item value="get Display String" />
+      <item value="Wrap [generator] as a [Builder] that generates Dart library files. [generatedExtension] indicates what files will be created for each `.dart` input. Defaults to `.g.dart`, however this should usually be changed to avoid conflicts with outputs from a [SharedPartBuilder]. If [generator] will create additional outputs through the [BuildStep] they should be indicated in [additionalOutputExtensions]. [formatOutput] is called to format the generated code. Defaults to [DartFormatter.format]. [header] is used to specify the content at the top of each generated file. If `null`, the content of [defaultFileHeader] is used. If [header] is an empty `String` no header is added. [allowSyntaxErrors] indicates whether to allow syntax errors in input libraries." />
+      <item value="A builder that positions the [firstChild] and [secondChild] widgets. The widget returned by this method is wrapped in an [AnimatedSize]. By default, this uses [AnimatedCrossFade.defaultLayoutBuilder], which uses a [Stack] and aligns the `bottomChild` to the top of the stack while providing the `topChild` as the non-positioned child to fill the provided constraints. This works well when the [AnimatedCrossFade] is in a position to change size and when the children are not flexible. However, if the children are less fussy about their sizes (for example a [CircularProgressIndicator] inside a [Center]), or if the [AnimatedCrossFade] is being forced to a particular size, then it can result in the widgets jumping about when the cross-fade state is changed." />
+      <item value="Typically, the Directionality widget is introduced by the MaterialApp or WidgetsApp widget at the top of your application widget tree. It determines the ambient reading direction and is used, for example, to determine how to lay out text, how to interpret &quot;start&quot; and &quot;end&quot; values, and to resolve EdgeInsetsDirectional, AlignmentDirectional, and other Directional objects. Instead of providing a Directionality widget, another solution would be passing a non-directional 'alignment', or an explicit 'textDirection', to the Stack." />
       <item value="temporarily" />
       <item value="The network is temporarily good for the server connection network" />
       <item value="fix: fix wrong logic when no user info fetched caused by bad network." />
@@ -50,11 +55,6 @@
       <item value="Text Input Formatter" />
       <item value="过时" />
       <item value="Refactory" />
-      <item value="ecg binary" />
-      <item value="Converts the given JSON-string [input] to its corresponding object. Parsed JSON values are of the types [num], [String], [bool], [Null], [List]s of parsed JSON values or [Map]s from [String] to parsed JSON values. If `this` was initialized with a reviver, then the parsing operation invokes the reviver on every object or list property that has been parsed. The arguments are the property name ([String]) or list index ([int]), and the value is the parsed value. The return value of the reviver is used as the value of that property instead the parsed value. Throws [FormatException] if the input is not valid JSON text." />
-      <item value="portrait" />
-      <item value="signal Frequency" />
-      <item value="emergency" />
     </histories>
     <option name="languageScores">
       <map>
@@ -66,7 +66,7 @@
     </option>
   </component>
   <component name="Cache">
-    <option name="lastTrimTime" value="1632414702394" />
+    <option name="lastTrimTime" value="1632378694918" />
   </component>
   <component name="Settings">
     <option name="googleTranslateSettings">