in-model configs, show config options in prologue #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this branch, configurations can be specified directly inside of models. The configs work exactly the same as configs inside of the
dbt_project.yml
file.An in-model-config looks like this:
The config options are injected into the existing configs (more on this below) and the
config(...)
function call is replaced with a SQL comment containing the injected config options, eg:If the model is in your package, then config resolution works in the following order (later configs overwrite previous configs):