You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* initial commit
* remove ref to dockerized MS SQL container
* consolidate Dockerfile
* drop compose file
* move to it's own dir
* simplify
* egg= be nuts
* more settings
* add more extensions
* drop commented-out settings
* add additional packages
* move dbt power user to recommended
* flatten structure?
* add sqlfluff
* formatting json
* drop pylance preference
* move to recommended
* experiment
* no longer needed bc env is set
* auto start terminal with dbt build
* add PR dbt version back for CI tests
* oopsie type
* add docs
* Update README.md
* Update README.md
5. Decide whether you'd like to use the Web IDE or open the codespace in your local environment
172
+
6. When the codespace opens, a Task pane will show up and call `dbt build` just to show you how it's done
173
+
7. Decide whether or not you'd like the **dbt Power User extension** installed
174
+
8. Open up a new terminal and type `dbt build`!
175
+
9. Explore some of the bells and whistles (see below)
176
+
177
+
If you don't have Codespaces or would like to just run the environment in a local Docker container, you can by:
178
+
1. Having Docker Desktop installed
179
+
2. Install the "Remote - Containers" extension"
180
+
2. Clone the repo and open it in VSCode
181
+
3. Click **Reopen in Container** and wait for container to spin up
182
+

183
+
4. Continue from step 6 above
184
+
185
+
186
+
#### bells and whistles
187
+
188
+
There's some bells and whistles defined in the [.devcontainer.json]().devcontainer.json) that are worth calling out. Also a great reference is the [Setting up VSCode for dbt](https://dbt-msft.github.io/dbt-msft-docs/docs/guides/vscode_setup/) guide.
189
+
190
+
1. there is syntax highlighting provided by the `vdcode-dbt` extension. However, it is configured such that files in your `target/run` and `target/compiled` folder are not syntax highlighted, as a reminder that these files are not where you should be making changes!
191
+
2. basic `sqlfluff` linting is enabled as you type. Syntax errors will be underlined in red at the error, and will also be surfaced in the **Problems** tab of the Terminal pane. It's configured to lint as you type.
192
+
3. Autocompletion is enabled for generic dbt macros via the `vdcode-dbt` extension. For example, if you type `macro` you'll notice a pop up that you can select with the arrow keys then click tab to get a macro snippet.
4. the `find-related` extension allows an easy shortcut to navigating using `CMD`+`R`to jump from
196
+
- a model file to it's corresponding compiled version,
197
+
- from a compiled file to either the original model file or the version in `target/run`
161
198
162
199
200
+
</details>
201
+
163
202
### Step-by-step explanation
164
203
165
204
To get up and running with this project:
@@ -247,6 +286,8 @@ To get up and running with this project:
247
286
```
248
287
</details>
249
288
289
+
290
+
250
291
*Why a 2nd activation of the virtual environment?*
251
292
<details>
252
293
<summary>This may not be necessary for many users, but might be for some. Read on for a first-person report from @dbeatty10.</summary>
@@ -392,6 +433,13 @@ This is a known issue in DuckDB. If you are using DBeaver, this means shutting d
392
433
393
434
Very worst-case, deleting the database file will get you back in action (BUT you will lose all your data).
394
435
436
+
437
+
#### GitHub Codespaces and VSCode Remote Container
438
+
439
+
If you're using a privacy-forward browser such as Firefox and Brave, or a tracking-cookie-blocking extension like UBlock Origin or Privacy Badger, you may see the below error. You can either change your cookie settings, use a browser like Chrome, or just ignore the error because it doesn't affect the demo
0 commit comments