Editor settings

The editor settings supported by ty's language server, as well as the settings specific to ty's VS Code extension.

`configuration`

In-editor configuration of ty's settings. The inline settings always take precedence over the settings from configuration files, including the configuration specified with configurationFile.

Consult the configuration reference for a list of all supported configuration options.

Default value: null

Type: object

Example usage:

=== "VS Code"

```json
{
  "ty.configuration": {
    "rules": {
      "unresolved-reference": "warn"
    }
  }
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      configuration = {
        rules = {
          ["unresolved-reference"] = "warn"
        }
      }
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      configuration = {
        rules = {
          ["unresolved-reference"] = "warn"
        }
      }
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "configuration": {
           "rules": {
            "unresolved-reference": "warn"
          }
        }
      }
    }
  }
}
```

`configurationFile`

The path to a ty.toml configuration file. ty will use the specified configuration over any automatically discovered configuration. ty will expand a tilde ~ at the start of a string to the user's home directory, as well as variables like $A or ${A}.

!!! info

While ty configuration can be included in a `pyproject.toml` file, it is not allowed in this context.

Default value: null

Type: string

Example usage:

=== "VS Code"

```json
{
  "ty.configurationFile": "./.config/ty.toml"
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      configurationFile = "./.config/ty.toml"
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      configurationFile = "./.config/ty.toml"
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "configurationFile": "./.config/ty.toml"
      }
    }
  }
}
```

`disableLanguageServices`

Whether to disable the language services for the ty language server like code completion, hover, go to definition, etc.

This is useful if you want to use ty exclusively for type checking and want to use another language server for features like code completion, hover, go to definition, etc.

Default value: false

Type: boolean

Example usage:

=== "VS Code"

```json
{
  "ty.disableLanguageServices": true
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      disableLanguageServices = true,
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      disableLanguageServices = true,
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "disableLanguageServices": true
      }
    }
  }
}
```

`diagnosticMode`

Determines the scope of the diagnostics reported by the language server.

Setting this to off is useful if you want to use ty exclusively for the language server features like code completion, hover, go to definition, etc.

off: Diagnostics are disabled.
openFilesOnly: Diagnostics are reported only for files that are currently open in the editor.
workspace: Diagnostics are reported for all files in the workspace.

Default value: "openFilesOnly"

Type: "off" | "workspace" | "openFilesOnly"

Example usage:

=== "VS Code"

```json
{
  "ty.diagnosticMode": "workspace"
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      diagnosticMode = 'workspace',
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      diagnosticMode = 'workspace',
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "diagnosticMode": "workspace"
      }
    }
  }
}
```

`showSyntaxErrors`

Whether to show syntax error diagnostics.

This is useful when using ty with other language servers, allowing the user to refer to syntax errors from only one source.

Default value: true

Type: bool

Example usage:

=== "VS Code"

```json
{
    "ty.showSyntaxErrors": false
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      showSyntaxErrors = false,
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      showSyntaxErrors = false,
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "showSyntaxErrors": false
      }
    }
  }
}
```

`inlayHints`

These settings control the inline hints that ty provides in an editor.

`variableTypes`

Whether to show the types of variables as inline hints.

Default value: true

Type: boolean

Example usage:

=== "VS Code"

```json
{
  "ty.inlayHints.variableTypes": false
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      inlayHints = {
        variableTypes = false,
      },
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      inlayHints = {
        variableTypes = false,
      },
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "inlayHints": {
          "variableTypes": false
        }
      }
    }
  }
}
```

`callArgumentNames`

Whether to show argument names in call expressions as inline hints.

Default value: true

Type: boolean

Example usage:

=== "VS Code"

```json
{
  "ty.inlayHints.callArgumentNames": false
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      inlayHints = {
        callArgumentNames = false,
      },
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      inlayHints = {
        callArgumentNames = false,
      },
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "inlayHints": {
          "callArgumentNames": false
        }
      }
    }
  }
}
```

`completions`

These settings control how code completions offered by ty work.

`autoImport`

Whether to include auto-import suggestions in code completions. That is, code completions will include symbols not currently in scope but available in your environment.

Default value: true

Type: boolean

Example usage:

=== "VS Code"

```json
{
  "ty.completions.autoImport": true
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  settings = {
    ty = {
      completions = {
        autoImport = true,
      },
    },
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  settings = {
    ty = {
      completions = {
        autoImport = true,
      },
    },
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "settings": {
        "completions": {
          "autoImport": true
        }
      }
    }
  }
}
```

VS Code specific

The following settings are specific to ty's VS Code extension.

`importStrategy`

Strategy for loading the ty executable.

fromEnvironment finds ty in the environment, falling back to the bundled version
useBundled uses the version bundled with the extension

Default value: "fromEnvironment"

Type: "fromEnvironment" | "useBundled"

Example usage:

json

{
  "ty.importStrategy": "useBundled"
}

`interpreter`

A list of paths to Python interpreters. Even though this is a list, only the first interpreter is used.

The interpreter path is used to find the ty executable when ty.importStrategy is set to fromEnvironment.

Default value: []

Type: string[]

Example usage:

json

{
  "ty.interpreter": ["/home/user/.local/bin/python"]
}

`path`

A list of path to ty executables.

The extension uses the first executable that exists. This setting takes precedence over the ty.importStrategy setting.

Default value: []

Type: string[]

Example usage:

json

{
  "ty.path": ["/home/user/.local/bin/ty"]
}

`trace.server`

The detail level at which messages between the language server and the editor (client) are logged.

This setting is useful for debugging issues with the language server. Refer to the troubleshooting guide in ty's VS Code extension for more information.

Default value: "off"

Type: "off" | "messages" | "verbose"

Example usage:

json

{
  "ty.trace.server": "messages"
}

Initialization options

The following settings are required when ty is initialized in an editor. These settings are static so changing them requires restarting the editor to take effect.

For VS Code users, these settings are defined in the ty.* namespace as usual, but for other editors, they would need to be provided in a separate field of the configuration that corresponds to the initialization options. Refer to the examples below for how to set these options in different editors.

`logFile`

Path to the file to which the language server writes its log messages. By default, ty writes log messages to stderr.

Default value: null

Type: string

Example usage:

=== "VS Code"

```json
{
  "ty.logFile": "/path/to/ty.log"
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  init_options = {
    logFile = '/path/to/ty.log',
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  init_options = {
    logFile = '/path/to/ty.log',
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "initialization_options": {
        "logFile": "/path/to/ty.log"
      }
    }
  }
}
```

`logLevel`

The log level to use for the language server.

Default value: "info"

Type: "trace" | "debug" | "info" | "warn" | "error"

Example usage:

=== "VS Code"

```json
{
  "ty.logLevel": "debug"
}
```

=== "Neovim"

```lua
-- Neovim >=0.11:
vim.lsp.config('ty', {
  init_options = {
    logLevel = 'debug',
  },
})

-- Neovim <0.11:
require('lspconfig').ty.setup({
  init_options = {
    logLevel = 'debug',
  },
})
```

=== "Zed"

```json
{
  "lsp": {
    "ty": {
      "initialization_options": {
        "logLevel": "debug"
      }
    }
  }
}
```