Interactive Compile #3179
Interactive Compile #3179
Conversation
✅ Deploy Preview for docs-getdbt-com ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
github-actions
bot
added
content
| It is _not_ a pre-requisite of `dbt run`. | ||
| <VersionBlock firstVersion="1.5"> | ||
|
|
||
| Starting in dbt v1.5, `compile` becomes interactive in the CLI using the selection syntaxt `--select` or `--inline` to target specic models or Jinja references, respectively. This will return the compiled SQL in the CLI (in addition to the `target/` directory). |
There was a problem hiding this comment.
Nit: syntaxt → syntax
specic → specific
return the compiled SQL in the CLI → display the compiled SQL inline in the terminal.
| @@ -11,4 +11,22 @@ The `compile` command is useful for: | |||
| 2. Manually running compiled SQL. While debugging a model or schema test, it's often useful to execute the underlying `select` statement to find the source of the bug. | |||
| 3. Compiling `analysis` files. Read more about analysis files [here](/docs/build/analyses). | |||
|
|
|||
| It is _not_ a pre-requisite of `dbt run`. | |||
| <VersionBlock firstVersion="1.5"> | |||
There was a problem hiding this comment.
What's the convention around what to put in the version block? I'd assume it was only highlighting that this is net new behavior, and documenting below outside the version block.
There was a problem hiding this comment.
We deprecated the use of changelogs in favor of version blocks to help reign in the amount of information displayed on the screen. Since we version the docs themselves, this makes a generally more pleasing UX, and gives us a nice way to dynamically change the content (where appropriate) for different product versions.
What are you changing in this pull request and why?
Updating the
compiledocuments to reflect enhancements made in dbt Core v1.5Checklist
Add versioning components, as described in Versioning Docs
Review the Content style guide and About versioning so my content adheres to these guidelines.
resolves #2994