This branch was auto-updated!

dbt-labs · Feb 23, 2024 · 417f6e1 · 417f6e1
2 parents db6bf1e + 48d2da3
commit 417f6e1
Show file tree

Hide file tree

Showing 5 changed files with 26 additions and 3 deletions.
diff --git a/website/docs/docs/build/custom-aliases.md b/website/docs/docs/build/custom-aliases.md
@@ -127,6 +127,9 @@ The default implementation of `generate_alias_name` simply uses the supplied `al
 
 </VersionBlock>
 
+import WhitespaceControl from '/snippets/_whitespace-control.md';
+
+<WhitespaceControl/>
 
 ### Dispatch macro - SQL alias management for databases and dbt packages
 

diff --git a/website/docs/docs/build/custom-databases.md b/website/docs/docs/build/custom-databases.md
@@ -85,6 +85,10 @@ The default implementation of `generate_database_name` simply uses the supplied
 
 </File>
 
+import WhitespaceControl from '/snippets/_whitespace-control.md';
+
+<WhitespaceControl/>
+
 <VersionBlock firstVersion="1.6">
 
 ### Managing different behaviors across packages

diff --git a/website/docs/docs/build/custom-schemas.md b/website/docs/docs/build/custom-schemas.md
@@ -83,6 +83,12 @@ The following code represents the default macro's logic:
 
 {%- endmacro %}
 ```
+<br />
+
+import WhitespaceControl from '/snippets/_whitespace-control.md';
+
+<WhitespaceControl/>
+
 
 ## Changing the way dbt generates a schema name
 
@@ -92,8 +98,7 @@ To customize this macro, copy the example code in the section [How does dbt gene
 
 Be careful. dbt will ignore any custom `generate_schema_name` macros included in installed packages.
 
-<details>
-<summary>❗️ Warning: Don't replace <code>default_schema</code> in the macro.</summary>
+<expandable alt_header="Warning: Don't replace `default_schema` in the macro">
 
 If you're modifying how dbt generates schema names, don't just replace ```{{ default_schema }}_{{ custom_schema_name | trim }}``` with ```{{ custom_schema_name | trim }}``` in the ```generate_schema_name``` macro.
 
@@ -119,7 +124,7 @@ If you remove ```{{ default_schema }}```, it causes developers to override each
 
 ```
 
-</details>
+</expandable>
 
 ### generate_schema_name arguments
 

diff --git a/website/docs/docs/build/jinja-macros.md b/website/docs/docs/build/jinja-macros.md
@@ -124,6 +124,9 @@ from app_data.payments
 
 </File>
 
+import WhitespaceControl from '/snippets/_whitespace-control.md';
+
+<WhitespaceControl/>
 
 ### Using a macro from a package
 A number of useful macros have also been grouped together into [packages](/docs/build/packages) — our most popular package is [dbt-utils](https://hub.getdbt.com/dbt-labs/dbt_utils/latest/).

diff --git a/website/snippets/_whitespace-control.md b/website/snippets/_whitespace-control.md
@@ -0,0 +1,8 @@
+<details>
+<summary>💡 Use Jinja's whitespace control to tidy your macros!</summary>
+
+When you're modifying macros in your project, you might notice extra white space in your code in the `target/compiled` folder.
+
+You can remove unwanted spaces and lines with Jinja's [whitespace control](/faqs/Jinja/jinja-whitespace) by using a minus sign. For example, use `{{- ... -}}` or `{%- ... %}` around your macro definitions (such as `{%- macro generate_schema_name(...) -%} ... {%- endmacro -%}`).
+
+</details>