add selector for python models, creating default node color in DAG visualization

[paulbenschmidt]

resolves dbt-labs/dbt-core#5880

Description

Changes default color assignment of Python models in lineage graph so that they're easily distinguishable from SQL models. After scanning the current colors, I figured that some type of yellow would be the safest bet; I'm including a few variations below...

#e3ad06 (proposed) - it looks a little like mustard, but I wanted it to be dark enough for the characters to contrast

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[emmyoop]

@paulbenschmidt thanks for this contribution! I tested it out and everything looks great and works just as expected.

Is your email associated with your github handle? I checked our cla database and your handle is there as expected.

You'll also need to add a changelog entry. Seems like our docs are missing that piece of info! You can use the instructions here.

@jtcohen6 or @lostmygithubaccount can I get your input on the default node color, please?

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[paulbenschmidt]

@paulbenschmidt thanks for this contribution! I tested it out and everything looks great and works just as expected.

You'll also need to add a changelog entry. Seems like our docs are missing that piece of info! You can use the instructions here.

@jtcohen6 or @lostmygithubaccount can I get your input on the default node color, please?

Thank you, @emmyoop! I revised the color so that it was darker and contrasted more with the white text. I also added a changlelog entry!

Is your email associated with your github handle?

It is! I'm not sure why I can't get the error to disappear...

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Paul Schmidt.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[emmyoop]

@paulbenschmidt it looks like one of your commits was associated with a different email. You can either squash all your commits down to a single commit or you can create a new fork and move all your changes there with a new PR. That should resolve the CLA issue.

[paulbenschmidt]

@emmyoop - Thanks for the help! Squashing the commits did it! If you want me to start fresh in a new branch so that it's a bit cleaner, let me know!

[emmyoop]

@paulbenschmidt that's great news! We squash all the commits down when we merge anyways so this is a fine solution. Once I get some feedback from @lostmygithubaccount or @jtcohen6 on the default color we will be good to merge!

[lostmygithubaccount]

thanks for this contribution @paulbenschmidt!

I think keeping in line with our blue-ish color scheme in the DAG, it'd be better to make this a more subtle blue variant by default. would you (or @emmyoop?) mind updating to another color? perhaps a "SlateBlue"? hex code #6A5ACD

I haven't actually had a chance to see it myself. post-Coalesce, I think we'll consult with our design team on a default color scheme

[emmyoop]

I've created #325 to track revisiting the color scheme as a whole.

@paulbenschmidt, once you get the color updated to #6A5ACD this will be good to go!

[paulbenschmidt]

@emmyoop - Done! Example screenshot included below...

[emmyoop]

Thanks so much @paulbenschmidt for this contribution! Can't wait to see your next one 😃