Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CT-2201] DAG visualization: visually distinguish models based on 'access' #378

Closed
Tracked by #6747
MichelleArk opened this issue Feb 1, 2023 · 1 comment · Fixed by #389
Closed
Tracked by #6747

[CT-2201] DAG visualization: visually distinguish models based on 'access' #378

MichelleArk opened this issue Feb 1, 2023 · 1 comment · Fixed by #389

Comments

@MichelleArk
Copy link
Contributor

No description provided.

@github-actions github-actions bot changed the title DAG visualization: visually distinguish public vs private models [CT-1995] DAG visualization: visually distinguish public vs private models Feb 1, 2023
@emmyoop
Copy link
Member

emmyoop commented Feb 6, 2023

Maybe use a border.

@emmyoop emmyoop transferred this issue from dbt-labs/dbt-core Feb 27, 2023
@github-actions github-actions bot changed the title [CT-1995] DAG visualization: visually distinguish public vs private models [CT-2201] [CT-1995] DAG visualization: visually distinguish public vs private models Feb 27, 2023
@emmyoop emmyoop changed the title [CT-2201] [CT-1995] DAG visualization: visually distinguish public vs private models [CT-2201] DAG visualization: visually distinguish public vs private models Feb 27, 2023
@MichelleArk MichelleArk changed the title [CT-2201] DAG visualization: visually distinguish public vs private models [CT-2201] DAG visualization: visually distinguish models based on their 'access' configuration Feb 27, 2023
@MichelleArk MichelleArk changed the title [CT-2201] DAG visualization: visually distinguish models based on their 'access' configuration [CT-2201] DAG visualization: visually distinguish models based on 'access' Feb 27, 2023
@emmyoop emmyoop self-assigned this Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants