deploy: 849e791

Author: copybara-service

front_end/core/i18n/locales/generated/collected-ui-strings.d

@@ -38,6 +38,7 @@ export declare class AiCodeCompletion {
     }>;
     remove(): void;
     static isAiCodeCompletionEnabled(locale: string): boolean;
+    static isAiCodeCompletionStylesEnabled(locale: string): boolean;
 }
 export declare const enum ContextFlavor {
     CONSOLE = "console",// generated code can contain console specific APIs like `$0`.

front_end/models/ai_code_completion/AiCodeCompletion.d.ts

@@ -47,6 +47,18 @@ interface ChatWidgetInput extends Props {
     handleSuggestionClick: (title: string) => void;
     handleMessageContainerRef: (el: Element | undefined) => void;
 }
+/**
+ * ChatView is a web component for historical reasons and generally should not
+ * exist because it barely has any presenter logic and it is definitely not
+ * re-usable as a custom element. Instead, the template from ChatView should be
+ * embdedded into the AiAssistancePanel (the sole host of chat interfaces) and
+ * the scroll handling logic should be implemented in view functions using refs
+ * or re-usable custom elements. Currently, the ChatView just combines the
+ * interfaces of ChatMessage and ChatInput presenters and passes most of the
+ * properties down to those presenters as-is.
+ *
+ * @deprecated
+ */
 export declare class ChatView extends HTMLElement {
     #private;
     constructor(props: Props, view?: View);