vscode-dbt-power-user icon indicating copy to clipboard operation
vscode-dbt-power-user copied to clipboard

This extension makes vscode seamlessly work with dbt™: Auto-complete, preview, column lineage, AI docs generation, health checks, cost estimation etc

Results 248 vscode-dbt-power-user issues
Sort by recently updated
recently updated
newest added

## Overview ### Problem https://github.com/AltimateAI/vscode-dbt-power-user/issues/1241 ### Solution Implementing a new button to export the lineage diagram ### Screenshot/Demo A picture is worth a thousand words. Please highlight the changes if...

### Describe the feature It would be great to be able to type expand out any `SELECT *` statements to be a select statements with the columns explicitly listed. Preferably,...

enhancement
sweep

### Details Remove the legacy lineage UX code. ### Branch master

sweep

### Describe the feature dbt allows to add metadata to the model yaml files on the table and column level: https://docs.getdbt.com/reference/resource-configs/meta It would be nice if the documentation editor supports...

enhancement

### Describe the feature The lineage diagrams in the new UX are beautiful. It would be helpful to be able to export them, preferably as SVG. ### Describe alternatives you've...

enhancement

### Describe the feature The support for exposures in the lineage is great :) It would be good to have a shortcut to build all the models in a exposure....

enhancement

### Expected behavior Hey, I've just installed this extension and tried to use its column lineage feature as detailed here: https://docs.myaltimate.com/test/lineage/ ### Actual behavior When I select a column the...

bug

### Describe the feature When I choose a model and look at its lineage diagram, I'd like an option to: (1) fully expand from the current node to all its...

enhancement

### Describe the feature Currently when we look at the lineage of child or parent models, then we can not reduce them. We can keep adding parent or child tables,...

enhancement

### Expected behavior Order of columns should be preserved as in schema.yml when saving from docs editor ### Actual behavior Order of columns is changed in schema.yml when saving from...

bug