Added dbt labels as part of columns info when pushing decscriptions#41
Added dbt labels as part of columns info when pushing decscriptions#41aibunny wants to merge 6 commits intoslidoapp:mainfrom
Conversation
|
@aibunny Thanks for contributing, appreciate it! As mentioned in #40, I think it needs to be put under Moreover, this should be also added to the opposite way, i.e. from dbt to Superset. Could you please look into that as well? |
Thanks lemme do that. |
Pefect, thanks!
Ignore me, I misread the code changes. |
|
ok, done |
one-data-cookie
left a comment
There was a problem hiding this comment.
@aibunny Thanks again! Leaving a few comments. 😉
Also, would you mind summing up for me what sort of testing you performed?
|
|
||
| assert datasets, "There are no datasets in Superset!" | ||
|
|
||
There was a problem hiding this comment.
Would you mind removing the extra whitespaces to keep it aligned with the rest of the code?
There was a problem hiding this comment.
Could you please also remove the added whitespace from the rest of your changes?
|
|
||
| column_new['description'] = description | ||
|
|
||
| # Check if 'meta' field exists in dbt_columns |
There was a problem hiding this comment.
Maybe you could merge this with a previous if to keep the code DRY? It basically does the same operations.
There was a problem hiding this comment.
Would you mind reflecting this one, please?
There was a problem hiding this comment.
Why do you check for expressions when getting column descriptions
Co-authored-by: Michal Koláček <57877739+one-data-cookie@users.noreply.github.com>
|
I ran some functional tests because I didn't have any other tests to work with. Basically, I tested different cases: one with a metafield and labels, another with a metafield but no labels, and finally, a scenario with no metafield at all. |
You mean against dbt and Superset? Which versions did you use? Did it work as expected then? |
yes , I used dbt 1.7 and superset api v1 |
The labels are added in this format which I noticed is commonly used: