fix: prettier

Author: RomneyDa

CONTRIBUTING.md

@@ -60,6 +60,7 @@ Continue is quickly adding features, and we'd love to hear which are the most im
 an enhancement are:
 
 - Create an issue
+
   - First, check whether a similar proposal has already been made
   - If not, [create an issue](https://github.com/continuedev/continue/issues)
   - Please describe the enhancement in as much detail as you can, and why it would be useful
@@ -145,6 +146,7 @@ npm i -g vite
    `install-all-dependencies`
 
 2. Start debugging:
+
    1. Switch to Run and Debug view
    2. Select `Launch extension` from drop down
    3. Hit play button

extensions/cli/AGENTS.md

@@ -18,25 +18,30 @@ This is a CLI tool for Continue Dev that provides an interactive AI-assisted dev
 ### Core Components
 
 1. **Entry Point** (`src/index.ts`): Main CLI logic with two modes:
+
    - **Headless mode**: Non-interactive mode for automation/CI
    - **TUI mode**: Terminal User Interface using Ink/React
    - **Standard mode**: Traditional readline-based chat interface
 
 2. **Authentication** (`src/auth/`): WorkOS-based authentication system
+
    - `ensureAuth.ts`: Handles authentication flow
    - `workos.ts`: WorkOS configuration and token management
 
 3. **Continue SDK Integration** (`src/continueSDK.ts`): Initializes the Continue SDK client with:
+
    - API key authentication
    - Assistant configuration (slug-based)
    - Organization support
 
 4. **Terminal UI** (`src/ui/`): React/Ink-based TUI components
+
    - `TUIChat.tsx`: Main chat interface component
    - `UserInput.tsx`: Input handling with multi-line support
    - `TextBuffer.ts`: Text display utilities
 
 5. **Tools System** (`src/tools/`): Built-in development tools including:
+
    - File operations (read, write, list)
    - Code search functionality
    - Terminal command execution

extensions/cli/CHAT_HISTORY_SERVICE_MIGRATION_PLAN.md

@@ -299,6 +299,7 @@ If issues arise during migration:
 1. **Streaming integration**: Most complex change
    - Mitigation: Extensive testing, gradual rollout
 2. **Remote mode**: Different state management
+
    - Mitigation: Test thoroughly, maintain compatibility
 
 3. **Performance**: Large histories might cause issues

extensions/cli/spec/config-loading.md

@@ -23,11 +23,13 @@ This document specifies the behavior of the CLI's configuration loading system,
 **When CLI is invoked, config source is determined in this order:**
 
 1. **CLI `--config` Flag** (highest priority)
+
    - File path (starts with `.`, `/`, `~`): Loads local YAML file
    - Assistant slug (`owner/package`): Fetches from Continue platform
    - Overrides any saved preferences
 
 2. **Saved Config URI** (if no `--config` flag)
+
    - Retrieved from authentication config
    - Converts `file://` URIs back to file paths
    - Converts `slug://` URIs back to assistant slugs

extensions/cli/spec/onboarding.md

@@ -8,6 +8,7 @@ When a user first runs `cn` in interactive mode, they will be taken through "onb
 
 1. If the --config flag is provided, load this config
 2. Otherwise, we will present the user with two options:
+
    - Log in with Continue: log them in, which will automatically create their assistant and then we can load the first assistant from the first org
    - Enter your Anthropic API key: let them enter the key, and then either create a ~/.continue/config.yaml with the following contents OR update the existing config.yaml to add the model
 

extensions/vscode/package-lock.json

@@ -343,8 +343,8 @@ export class VerticalDiffHandler implements vscode.Disposable {
 
     // Then, we insert our diff lines
     await this.editor.edit((editBuilder) => {
-      (editBuilder.replace(this.range, replaceContent),
-        { undoStopAfter: false, undoStopBefore: false });
+      editBuilder.replace(this.range, replaceContent),
+        { undoStopAfter: false, undoStopBefore: false };
     });
 
     // Lastly, we apply decorations

extensions/vscode/src/diff/vertical/handler.ts

@@ -147,9 +147,7 @@ function ModelCard(props: ModelCardProps) {
           <h3>{props.title}</h3>
         </div>
 
-        {props.tags?.map((tag, i) => (
-          <ModelProviderTag key={i} tag={tag} />
-        ))}
+        {props.tags?.map((tag, i) => <ModelProviderTag key={i} tag={tag} />)}
 
         <p>{props.description}</p>