I hereby claim:
- I am beckjake on github.
- I am beckjake (https://keybase.io/beckjake) on keybase.
- I have a public key whose fingerprint is F979 644F 03B3 276D 5D60 6C92 D0BC F949 5593 59B8
To claim this, I am signing this object:
### Keybase proof | |
I hereby claim: | |
* I am beckjake on github. | |
* I am beckjake (https://keybase.io/beckjake) on keybase. | |
* I have a public key whose fingerprint is 749E 3A52 3347 E1A3 9971 03CE 9F5D CD08 29F2 6899 | |
To claim this, I am signing this object: |
I hereby claim:
To claim this, I am signing this object:
%YAML 1.2 | |
--- | |
name: dbt SQL | |
file_extensions: | |
- sql | |
scope: source.dbt | |
contexts: | |
main: | |
# the default context is SQL |
#!/usr/bin/env python | |
import argparse | |
import base64 | |
import code | |
import json | |
import pprint | |
import requests | |
When you dbt compile
, dbt at a very high level does this:
ref
, source
, and config
. The string result of the actual rendering is then discarded. The model's materialization type is finalized here, as are any other relevant model-level configuration items (database/schema/alias are easy examples here!).ref
information and use the command-line arguments to decide which nodes to iterate overimport dataclasses | |
@dataclasses.dataclass | |
class MyClass: | |
a: dataclasses.InitVar[int] | |
_a: int = dataclasses.field(init=False) | |
def __post_init__(self, a: int) -> None: | |
self._a = a |