From 7eb4d451f118f0b18a6ca0071f0c23dabb264be2 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Tue, 25 Apr 2023 14:01:21 +0800
Subject: [PATCH] AI-223.8836.35.2231.9923731 <debuggerx@debuggerx-e5 Update
 yiiguxing.translation.xml

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

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index a25589c..3802614 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -4,6 +4,10 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="The child can be at most as large as the available space (but is allowed to be smaller)." />
+      <item value="The child is forced to fill the available space." />
+      <item value="The [Flexible] widget assigns this kind of [FlexFit] to its child." />
+      <item value="The [Expanded] widget assigns this kind of [FlexFit] to its child." />
       <item value="A widget that sizes its child to the child's intrinsic height. This class is useful, for example, when unlimited height is available and you would like a child that would otherwise attempt to expand infinitely to instead size itself to a more reasonable height. The constraints that this widget passes to its child will adhere to the parent's constraints, so if the constraints are not large enough to satisfy the child's maximum intrinsic height, then the child will get less height than it otherwise would. Likewise, if the minimum height constraint is larger than the child's maximum intrinsic height, the child will be given more height than it otherwise would. This class is relatively expensive, because it adds a speculative layout pass before the final layout phase. Avoid using it where possible. In the worst case, this widget can result in a layout that is O(N²) in the depth of the tree." />
       <item value="remove Material Icons font to reduce deb package size." />
       <item value="Load Device's Contexts from the iOS SDK. This integration calls the iOS SDK via Message channel to load the Device's contexts before sending the event back to the iOS SDK via Message channel (already enriched with all the information). The Device's contexts are: App, Device and OS. ps. This integration won't be run on Android because the Device's Contexts is set on Android when the event is sent to the Android SDK via the Message channel. We intend to unify this behaviour in the future. This integration is only executed on iOS &amp; MacOS Apps." />
@@ -50,15 +54,11 @@
       <item value="If [forceRefresh] is `true`, the token returned will be refreshed regardless of token expiration." />
       <item value="A longer-lived native function, which occupies the thread calling it. Do not call these kind of native functions in the main isolate. They will block Dart execution. This will cause dropped frames in Flutter applications. Instead, call these native functions on a separate isolate." />
       <item value="A very short-lived native function. For very short-lived functions, it is fine to call them on the main isolate. They will block the Dart execution while running the native function, so only do this for native functions which are guaranteed to be short-lived." />
-      <item value="returns decoded [data] or throw [ReedSolomonException] if data cannot be decoded" />
-      <item value="Decodes a Qr code given the matrix of its raw bits." />
-      <item value="Extract the raw content of the QR code from an image BitMatrix, given the location." />
-      <item value="Get new content" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="96" />
-        <entry key="ENGLISH" value="97" />
+        <entry key="CHINESE" value="100" />
+        <entry key="ENGLISH" value="101" />
         <entry key="POLISH" value="1" />
       </map>
     </option>