From c5957edf4f2274d15492ac15d003d2fa94ddaa31 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Thu, 22 Jun 2023 20:51:09 +0800
Subject: [PATCH] AI-Flamingo | 2022.2.1 Patch 2 <debuggerx@debuggerx 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 865d364..e9e6bb0 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -1,9 +1,12 @@
 <application>
   <component name="Translation.Cache">
-    <option name="lastTrimTime" value="1686305738173" />
+    <option name="lastTrimTime" value="1687436735883" />
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="visit Library Directive" />
+      <item value="Return the result of resolving the file at the given [path]. If a [resourceProvider] is given, it will be used to access the file system. Note that if more than one file is going to be resolved then this function is inefficient. Clients should instead use [AnalysisContextCollection] to create one or more contexts and use those contexts to resolve the files." />
+      <item value="Return the result of parsing the file at the given [path]. If a [resourceProvider] is given, it will be used to access the file system. [featureSet] determines what set of features will be assumed by the parser. This parameter is required because the analyzer does not yet have a performant way of computing the correct feature set for a single file to be parsed. Callers that need the feature set to be strictly correct must create an [AnalysisContextCollection], query it to get an [AnalysisContext], query it to get an [AnalysisSession], and then call `getParsedUnit`. Callers that don't need the feature set to be strictly correct can pass in `FeatureSet.latestLanguageVersion()` to enable the default set of features; this is much more performant than using an analysis session, because it doesn't require the analyzer to process the SDK. If [throwIfDiagnostics] is `true` (the default), then if any diagnostics are produced because of syntactic errors in the file an `ArgumentError` will be thrown. If the parameter is `false`, then the caller can check the result to see whether there are any errors." />
       <item value="Returns the result of parsing the given [content] as a compilation unit. If a [featureSet] is provided, it will be the default set of features that will be assumed by the parser. If a [path] is provided, it will be used as the name of the file when reporting errors. If [throwIfDiagnostics] is `true` (the default), then if any diagnostics are produced because of syntactic errors in the [content] an `ArgumentError` will be thrown. This behavior is not intended as a way for the client to find out about errors--it is intended to avoid causing problems for naive clients that might not be thinking about the possibility of parse errors (and might therefore make assumptions about the returned AST that don't hold in the presence of parse errors). Clients interested in details about parse errors should pass `false` and check `result.errors` to determine what parse errors, if any, have occurred." />
       <item value="Platform Detector" />
       <item value="Returns the least significant [width] bits of this integer, extending the highest retained bit to the sign. This is the same as truncating the value to fit in [width] bits using an signed 2-s complement representation. The returned value has the same bit value in all positions higher than [width]." />
@@ -51,14 +54,11 @@
       <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." />
       <item value="Integration which handles communication with native frameworks in order to enrich [SentryTransaction] objects with app start data for mobile vitals." />
       <item value="We need to check the platform after we checked for web, because the OS checks return true when the browser runs on the checked platform. Example: platform.isAndroid return true if the browser is used on an Android device." />
-      <item value="Enable or disable the Crash handling on the Native SDKs, e.g., UncaughtExceptionHandler and [anrEnabled] for Android. SentryCrashIntegration (KSCrash) for iOS, turning this feature off on iOS has a side effect which is missing the Device's context, e.g., App, Device and Operation System. Disabling this feature affects the [enableAutoSessionTracking] feature, as this is required to mark Sessions as Crashed." />
-      <item value="Match the baseline of the placeholder with the baseline. The [TextBaseline] to use must be specified and non-null when using this alignment mode." />
-      <item value="How the placeholder aligns vertically with the text. See [ui.PlaceholderAlignment] for details on each mode." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="141" />
-        <entry key="ENGLISH" value="142" />
+        <entry key="CHINESE" value="144" />
+        <entry key="ENGLISH" value="145" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />
       </map>