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.

Sign up for GitHub

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 to our yaml style best practice guide #6662

Merged
merged 3 commits into from
Dec 13, 2024
Merged

add to our yaml style best practice guide #6662

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1e44a5e
Update 5-how-we-style-our-yaml.md
runleonarun Dec 13, 2024
96fa458
Update website/docs/best-practices/how-we-style/5-how-we-style-our-ya…
runleonarun Dec 13, 2024
3e09b42
Merge branch 'current' into runleonarun-patch-16
matthewshaver Dec 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions website/docs/best-practices/how-we-style/5-how-we-style-our-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ id: 5-how-we-style-our-yaml

- 2️⃣ Indents should be two spaces
- ➡️ List items should be indented
- 🔠 List items with a single entry can be a string. For example, `'select': 'other_user'`, but it's best practice to provide the argument as an explicit list. For example, `'select': ['other_user']`
- 🆕 Use a new line to separate list items that are dictionaries where appropriate
- 📏 Lines of YAML should be no longer than 80 characters.
- 🛠️ Use the [dbt JSON schema](https://github.com/dbt-labs/dbt-jsonschema) with any compatible IDE and a YAML formatter (we recommend [Prettier](https://prettier.io/)) to validate your YAML files and format them automatically.
Expand Down
Loading