Skip to content

Commit

Permalink
Remove some useless install instructions froom readme
Browse files Browse the repository at this point in the history
  • Loading branch information
bastienboutonnet committed Apr 13, 2020
1 parent fd8243a commit 80f3f67
Showing 1 changed file with 0 additions and 18 deletions.
18 changes: 0 additions & 18 deletions vscode-dbt/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,24 +12,6 @@ for loops, conditionals, blocks, variable settings etc. See [source](./vscode-db
ref, source, log, config etc. See [source](./vscode-dbt/snippets/snippets.json) for a full list.
![dbt_sql](./images/dbt_sql.gif)


## Requirements

- Syntax highlighting, and jinja comments `{# comment #}` formatting is extremely well implemented in the [Better Jinja VSCode extemsion](https://marketplace.visualstudio.com/items?itemName=samuelcolvin.jinjahtml). **You really should install it as this extension is meant to work for the language `jinja-sql` which is implemented in this extention**
- Once you have installed the Better Jinja extension you may want to associate your `.sql` files with the `jinja-sql` language that you do not have to select it every time **but this is entirely up to you and your use case**. For example, you may in some cases not want to write dbt-/jinja-flavoured SQL.
- To associate your `.sql` files with `jinja-sql` (optional but recommended) language add the following to your `settings.json` file:
```json
"files.associations":{
"*.sql":"jinja-sql",
}
```

## Installation
The package is currently not hosted on the VSCode Extension Marketplace. To install it:
1. Download the package from [here](https://github.com/bastienboutonnet/vscode-dbt/releases)
2. Unzip it into `~/.vscode/extensions` (or copy it somewhere and move it there).
4. Restart VSCode for your changes to take effect.

## Credits
### dbt jinja concepts
adapted from https://github.com/fishtown-analytics/atom-dbt/blob/master/snippets/dbt-sql.cson
Expand Down

0 comments on commit 80f3f67

Please sign in to comment.