-
Notifications
You must be signed in to change notification settings - Fork 975
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
Add style guide #3300
Add style guide #3300
Conversation
… into add-style-guide
✅ Deploy Preview for docs-getdbt-com ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really love this! It'll be nice to have a style guide that's cleaned up and distinct from the project structure guide.
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/2-how-we-style-our-sql.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/2-how-we-style-our-sql.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/2-how-we-style-our-sql.md
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/4-how-we-style-our-jinja.md
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/0-how-we-style-our-dbt-projects.md
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Outdated
Show resolved
Hide resolved
## Fields and model names | ||
|
||
- 👥 Models should be pluralized, e.g. `customers`, `orders`, `products`. | ||
- 🔑 Each model should have a primary key. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have opinions about whether this is a single column (implying dbt_utils.generate_surrogate_key(['region_id', 'user_id'])
) or are you OK with the two columns region_id
+ user_id
fulfilling this duty between them?
website/docs/guides/best-practices/how-we-style/1-how-we-style-our-dbt-models.md
Show resolved
Hide resolved
@@ -0,0 +1,39 @@ | |||
--- | |||
title: How we style our python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this lowercase python
a specific choice? everywhere else it's capitalised but as the lowercase-your-proper-nouns company, I'm loath to immediately label this a typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good q -- @matthewshaver what's our official style stance here do we capitalize python?
website/docs/guides/best-practices/how-we-style/4-how-we-style-our-jinja.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/5-how-we-style-our-yaml.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/6-how-we-style-conclusion.md
Outdated
Show resolved
Hide resolved
website/docs/guides/best-practices/how-we-style/6-how-we-style-conclusion.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Co-authored-by: Joel Labes <joel.labes@dbtlabs.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s t y l e
What are you changing in this pull request and why?
Checklist
Adding new pages (delete if not applicable):
website/sidebars.js