# Catch errors with type checking

> Find unresolved tables and columns while you edit, check the whole pipeline before it runs, and run the same checks in CI.

Renart checks your SQL against the tables, columns and types your pipeline knows about. Problems show up in the editor as you type, and the **Type check** tab checks the whole pipeline, including the dashboards and reports built on it, before anything runs against your database.

![A SQL asset with a misspelled column underlined in red, and the Type check tab listing two errors and a warning with View source and Open columns links](https://getrenart.com/docs-media/type-check.webp)

## Fix problems while you edit

The editor underlines unresolved tables and columns as you type. Hover an underline to read the problem, for example **Unresolved column: countrie**. When Renart knows a likely match, the hover offers a quick fix such as **Change ‘countrie’ to ‘country’**. Press **Ctrl+.** with the cursor on the underline to apply it.

Completion helps you avoid these problems in the first place: after a table alias, it lists that table’s columns with their types.

## Check the whole pipeline

1. Open **Type check** in the results panel below the editor.
2. Read the summary: the number of errors and warnings, how many assets and presentations were checked, and the window used for templates.
3. Choose **View source** next to a problem to jump to it. A warning about declared columns, such as a query that no longer produces a column its definition declares, links to **Open columns**.
4. Choose **Re-run** after fixing the problems.

The Type check tab badge shows the number of open problems, so you can see them without opening the tab.

## Tables the pipeline does not know yet

The editor can also complete tables it has observed on the selected warehouse. Using one is allowed but flagged as a warning until a source asset represents it. Choose **Import source asset** from the warning or the Type check tab to review the table’s name, connection and columns before adding it, or add it from the [Data Browser](https://getrenart.com/docs/connections-environments/data-browser.md).

## Run the same checks in CI

`renart type-check` runs the same checks from the terminal and exits with code `1` when it finds errors. Add `--strict` to fail on warnings too. See the [CLI reference](https://getrenart.com/docs/reference/cli.md#renart-type-check) for all options.

## Related

- [SQL assets](https://getrenart.com/docs/asset-types/sql-assets.md): writing the query and declaring its columns.
- [Variables and Jinja in SQL](https://getrenart.com/docs/editing-assets/variables-and-jinja.md): templated SQL is checked after rendering.
- [The asset editor](https://getrenart.com/docs/editing-assets/asset-editor.md): the rest of the results panel.