From 1dd39b32198c57089561c8c24524f11c27eabed3 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Mon, 21 Feb 2022 14:52:19 +0800
Subject: [PATCH] AI-Bumblebee | 2021.1.1 Patch 1 <debuggerx@debuggerx-PC
 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 7d413c5..c1d14ae 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -5,6 +5,7 @@
     <option name="newTranslationDialogY" value="624" />
     <option name="pinNewTranslationDialog" value="true" />
     <histories>
+      <item value="feat: add startup bulletin; switch to edit mode when click text on md preview." />
       <item value="on Tap" />
       <item value="Handles errors emitted by this [Future]. This is the asynchronous equivalent of a &quot;catch&quot; block. Returns a new [Future] that will be completed with either the result of this future or the result of calling the `onError` callback. If this future completes with a value, the returned future completes with the same value. If this future completes with an error, then [test] is first called with the error value. If `test` returns false, the exception is not handled by this `catchError`, and the returned future completes with the same error and stack trace as this future. If `test` returns `true`, [onError] is called with the error and possibly stack trace, and the returned future is completed with the result of this call in exactly the same way as for [then]'s `onError`. If `test` is omitted, it defaults to a function that always returns true. The `test` function should not throw, but if it does, it is handled as if the `onError` function had thrown. Note that futures don't delay reporting of errors until listeners are added. If the first `catchError` (or `then`) call happens after this future has completed with an error then the error is reported as unhandled error. See the description on [Future]. The `Function` below stands for one of two types: - (dynamic) -&gt; FutureOr&lt;T&gt; - (dynamic, StackTrace) -&gt; FutureOr&lt;T&gt; Given that there is a `test` function that is usually used to do an `isCheck` we should also expect functions that take a specific argument." />
       <item value="catch Error" />
@@ -54,12 +55,11 @@
       <item value="conflict" />
       <item value="precondition Failed" />
       <item value="request Entity Too Large" />
-      <item value="request Uri Too Long" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="151" />
-        <entry key="ENGLISH" value="152" />
+        <entry key="CHINESE" value="152" />
+        <entry key="ENGLISH" value="153" />
         <entry key="AFRIKAANS" value="1" />
         <entry key="LATIN" value="1" />
         <entry key="ROMANIAN" value="1" />