sqlmesh 0.209.1.dev10__tar.gz → 0.209.1.dev12__tar.gz

sqlmesh-0.209.1.dev12/.claude/agents/qa-reviewer.md

@@ -0,0 +1,106 @@
+---
+name: qa-reviewer
+description: Use this agent PROACTIVELY when you need to analyze a PR or code changes to provide structured QA testing guidance for human QA testers. This agent reviews PRs and provides specific testing scenarios, example projects to use, commands to run, and validation steps. Examples: <example>Context: A developer just implemented virtual environment isolation for SQLMesh. user: 'I just added support for isolated virtual environments in SQLMesh' assistant: 'Let me use the qa-reviewer agent to create comprehensive QA testing instructions for this feature' <commentary>Since a significant feature was implemented, use the qa-reviewer agent to provide structured testing guidance for QA.</commentary></example> <example>Context: A PR adds a new SQL engine adapter. user: 'Here's the PR that adds BigQuery support to SQLMesh' assistant: 'I'll use the qa-reviewer agent to analyze this change and create QA test scenarios' <commentary>Since a new engine adapter was added, use the qa-reviewer agent to provide testing guidance specific to engine adapters.</commentary></example>
+tools: Glob, Grep, LS, Read, NotebookRead, WebFetch, TodoWrite, WebSearch, Bash
+model: sonnet
+color: green
+---
+
+You are a QA Test Specialist with deep expertise in SQLMesh's architecture, testing methodologies, and quality assurance practices. You specialize in analyzing code changes and providing comprehensive, structured testing guidance for human QA testers.
+
+Your core responsibilities:
+
+## Analysis Approach
+
+- Review PRs and code changes to understand the scope and impact of modifications
+- Identify all components, features, and workflows that could be affected by the changes
+- Consider edge cases, integration points, and potential failure scenarios
+- Map changes to existing example projects and testing workflows
+- Provide specific, actionable testing instructions that non-developers can follow
+- MUST write full instructions to the `plans/` folder with the filename of `<pr_number>_<short description>.md` so they can be reviewed and executed by QA testers
+
+## QA Test Plan Structure
+
+Organize your QA recommendations into clear, actionable sections:
+
+### **Change Summary**
+- Brief description of what was changed and why
+- Key components and files modified
+- Potential impact areas and affected workflows
+
+### **Test Environment Setup**
+- Which example project(s) to use for testing (e.g., `examples/sushi/`, `examples/sushi_dbt/`)
+- Any necessary environment configuration or setup steps
+- Required tools, databases, or dependencies
+
+### **Core Test Scenarios**
+- Step-by-step testing procedures with specific commands
+- Expected results and success criteria for each test
+- Validation commands to confirm expected behavior
+- Screenshots or output examples where helpful
+
+### **Edge Case Testing**
+- Boundary conditions and error scenarios to test
+- Negative test cases and expected failure modes
+- Cross-platform considerations (Windows/Linux/macOS)
+- Performance and scalability considerations
+
+### **Regression Testing**
+- Existing functionality that should be retested
+- Critical workflows that must continue working
+- Backward compatibility scenarios
+
+### **Integration Testing**
+- Cross-component testing scenarios
+- Multi-engine testing when relevant
+- dbt integration testing if applicable
+- UI/CLI integration points
+
+## Example Project Guidance
+
+Provide specific guidance on:
+- Which `examples/` project best demonstrates the feature
+- How to modify example projects for comprehensive testing
+- Custom test scenarios using real-world-like data
+- Commands to set up test scenarios and validate results
+
+## Command Examples
+
+Always provide:
+- Exact CLI commands to run tests
+- Configuration file modifications needed
+- Environment variable settings
+- Database setup commands when applicable
+- Validation queries or commands to check results
+
+## Testing Best Practices
+
+- Focus on user-facing functionality and workflows
+- Include both happy path and error scenarios
+- Provide clear success/failure criteria
+- Consider different user personas (data analysts, engineers, platform teams)
+- If the change doesn't have engine specific logic in it, prefer to test against duckdb since that is easiest
+- Include performance and scalability considerations
+- DO NOT have a step which is running an existing test - these tests are automatically run in CI and should not be duplicated in manual testing instructions
+- Assume all example projects are already tested as is and don't suggest doing a test which is running them again
+- All tests MUST just use `sqlmesh` cli commands - do not use the Python API. The goal is to run tests that mimic what an actual user would do, which is using the CLI.
+- A common pattern could be using the `sqlmesh` cli command and then running a Python script to validate the database or state is in an expected state, but the Python script should not be a test itself, just a validation step.
+
+## Communication Style
+
+- Use clear, numbered steps for testing procedures
+- Provide exact commands that can be copy-pasted
+- Include expected outputs and how to interpret results
+- Explain the "why" behind each test scenario
+- Use language accessible to QA testers who may not be developers
+- Organize content with clear headings and bullet points
+
+## Important Constraints
+
+- You NEVER write or modify code - you only analyze and provide testing guidance
+- You focus on user-facing functionality and workflows
+- You always provide specific, actionable testing steps
+- You consider the full user journey and realistic usage scenarios
+- You validate that your recommendations align with SQLMesh's architecture and patterns
+
+When analyzing changes, assume you're looking at a recent PR or set of code modifications. Focus on providing comprehensive testing guidance that ensures the changes work correctly, don't break existing functionality, and provide a good user experience across different scenarios and environments.

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/.pre-commit-config.yaml

@@ -7,7 +7,7 @@ repos:
         language: python
         types_or: [python, pyi]
         require_serial: true
-        files: &files ^(sqlmesh/|tests/|web/|examples/|setup.py)
+        files: &files ^(sqlmesh/|sqlmesh_dbt/|tests/|web/|examples/|setup.py)
       - id: ruff-format
         name: ruff-format
         entry: ruff format --force-exclude --line-length 100

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlmesh
-Version: 0.209.1.dev10
+Version: 0.209.1.dev12
 Summary: Next-generation data transformation framework
 Author-email: "TobikoData Inc." <engineering@tobikodata.com>
 License:                                  Apache License

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/pyproject.toml

@@ -142,6 +142,7 @@ risingwave = ["psycopg2"]
 
 [project.scripts]
 sqlmesh = "sqlmesh.cli.main:cli"
+sqlmesh_dbt = "sqlmesh_dbt.cli:dbt"
 sqlmesh_cicd = "sqlmesh.cicd.bot:bot"
 sqlmesh_lsp = "sqlmesh.lsp.main:main"
 
@@ -164,7 +165,7 @@ fallback_version = "0.0.0"
 local_scheme = "no-local-version"
 
 [tool.setuptools.packages.find]
-include = ["sqlmesh", "sqlmesh.*", "web*"]
+include = ["sqlmesh", "sqlmesh.*", "sqlmesh_dbt", "sqlmesh_dbt.*", "web*"]
 
 [tool.setuptools.package-data]
 web = ["client/dist/**"]

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/sqlmesh/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.209.1.dev10'
-__version_tuple__ = version_tuple = (0, 209, 1, 'dev10')
+__version__ = version = '0.209.1.dev12'
+__version_tuple__ = version_tuple = (0, 209, 1, 'dev12')
 
-__commit_id__ = commit_id = 'gab421d911'
+__commit_id__ = commit_id = 'g1237e9acd'

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/sqlmesh.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlmesh
-Version: 0.209.1.dev10
+Version: 0.209.1.dev12
 Summary: Next-generation data transformation framework
 Author-email: "TobikoData Inc." <engineering@tobikodata.com>
 License:                                  Apache License

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/sqlmesh.egg-info/SOURCES.txt

@@ -23,6 +23,7 @@ pyproject.toml
 .circleci/wait-for-db.sh
 .claude/agents/code-reviewer.md
 .claude/agents/developer.md
+.claude/agents/qa-reviewer.md
 .claude/agents/technical-writer.md
 .github/dependabot.yml
 .github/scripts/get_scm_version.py
@@ -489,6 +490,10 @@ sqlmesh/utils/pydantic.py
 sqlmesh/utils/rich.py
 sqlmesh/utils/windows.py
 sqlmesh/utils/yaml.py
+sqlmesh_dbt/__init__.py
+sqlmesh_dbt/cli.py
+sqlmesh_dbt/console.py
+sqlmesh_dbt/operations.py
 tests/.gitignore
 tests/__init__.py
 tests/conftest.py
@@ -596,6 +601,25 @@ tests/dbt/test_model.py
 tests/dbt/test_test.py
 tests/dbt/test_transformation.py
 tests/dbt/test_util.py
+tests/dbt/cli/conftest.py
+tests/dbt/cli/test_list.py
+tests/dbt/cli/test_operations.py
+tests/dbt/cli/test_run.py
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/dbt_project.yml
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/profiles.yml
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/customers.sql
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/docs.md
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/orders.sql
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/overview.md
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/schema.yml
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/staging/schema.yml
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/staging/stg_customers.sql
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/staging/stg_orders.sql
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/staging/stg_payments.sql
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/seeds/.gitkeep
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/seeds/raw_customers.csv
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/seeds/raw_orders.csv
+tests/dbt/cli/fixtures/jaffle_shop_duckdb/seeds/raw_payments.csv
 tests/dbt/converter/conftest.py
 tests/dbt/converter/test_convert.py
 tests/dbt/converter/test_jinja.py

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/sqlmesh.egg-info/entry_points.txt

@@ -1,4 +1,5 @@
 [console_scripts]
 sqlmesh = sqlmesh.cli.main:cli
 sqlmesh_cicd = sqlmesh.cicd.bot:bot
+sqlmesh_dbt = sqlmesh_dbt.cli:dbt
 sqlmesh_lsp = sqlmesh.lsp.main:main

{sqlmesh-0.209.1.dev10 → sqlmesh-0.209.1.dev12}/sqlmesh.egg-info/top_level.txt

@@ -1,2 +1,3 @@
 sqlmesh
+sqlmesh_dbt
 web

sqlmesh-0.209.1.dev12/sqlmesh_dbt/__init__.py

@@ -0,0 +1,5 @@
+# Note: `sqlmesh_dbt` is deliberately in its own package from `sqlmesh` to avoid the upfront time overhead
+# that comes from `import sqlmesh`
+#
+# Obviously we still have to `import sqlmesh` at some point but this allows us to defer it until needed,
+# which means we can make the CLI feel more responsive by being able to output something immediately

sqlmesh-0.209.1.dev12/sqlmesh_dbt/cli.py

@@ -0,0 +1,80 @@
+import typing as t
+import sys
+import click
+from sqlmesh_dbt.operations import DbtOperations, create
+
+
+def _get_dbt_operations(ctx: click.Context) -> DbtOperations:
+    if not isinstance(ctx.obj, DbtOperations):
+        raise ValueError(f"Unexpected click context object: {type(ctx.obj)}")
+    return ctx.obj
+
+
+@click.group()
+@click.pass_context
+def dbt(ctx: click.Context) -> None:
+    """
+    An ELT tool for managing your SQL transformations and data models, powered by the SQLMesh engine.
+    """
+
+    if "--help" in sys.argv:
+        # we dont need to import sqlmesh/load the project for CLI help
+        return
+
+    # TODO: conditionally call create() if there are times we dont want/need to import sqlmesh and load a project
+    ctx.obj = create()
+
+
+@dbt.command()
+@click.option("-s", "-m", "--select", "--models", "--model", help="Specify the nodes to include.")
+@click.option(
+    "-f",
+    "--full-refresh",
+    help="If specified, dbt will drop incremental models and fully-recalculate the incremental table from the model definition.",
+)
+@click.pass_context
+def run(ctx: click.Context, select: t.Optional[str], full_refresh: bool) -> None:
+    """Compile SQL and execute against the current target database."""
+    _get_dbt_operations(ctx).run(select=select, full_refresh=full_refresh)
+
+
+@dbt.command(name="list")
+@click.pass_context
+def list_(ctx: click.Context) -> None:
+    """List the resources in your project"""
+    _get_dbt_operations(ctx).list_()
+
+
+@dbt.command(name="ls", hidden=True)  # hidden alias for list
+@click.pass_context
+def ls(ctx: click.Context) -> None:
+    """List the resources in your project"""
+    ctx.forward(list_)
+
+
+def _not_implemented(name: str) -> None:
+    @dbt.command(name=name)
+    def _not_implemented() -> None:
+        """Not implemented"""
+        click.echo(f"dbt {name} not implemented")
+
+
+for subcommand in (
+    "build",
+    "clean",
+    "clone",
+    "compile",
+    "debug",
+    "deps",
+    "docs",
+    "init",
+    "parse",
+    "retry",
+    "run-operation",
+    "seed",
+    "show",
+    "snapshot",
+    "source",
+    "test",
+):
+    _not_implemented(subcommand)

sqlmesh-0.209.1.dev12/sqlmesh_dbt/console.py

@@ -0,0 +1,8 @@
+from sqlmesh.core.console import TerminalConsole
+
+
+class DbtCliConsole(TerminalConsole):
+    # TODO: build this out
+
+    def print(self, msg: str) -> None:
+        return self._print(msg)

sqlmesh-0.209.1.dev12/sqlmesh_dbt/operations.py

@@ -0,0 +1,133 @@
+from __future__ import annotations
+import typing as t
+from rich.progress import Progress
+from pathlib import Path
+
+if t.TYPE_CHECKING:
+    # important to gate these to be able to defer importing sqlmesh until we need to
+    from sqlmesh.core.context import Context
+    from sqlmesh.dbt.project import Project
+    from sqlmesh_dbt.console import DbtCliConsole
+
+
+class DbtOperations:
+    def __init__(self, sqlmesh_context: Context, dbt_project: Project):
+        self.context = sqlmesh_context
+        self.project = dbt_project
+
+    def list_(self) -> None:
+        for _, model in self.context.models.items():
+            self.console.print(model.name)
+
+    def run(self, select: t.Optional[str] = None, full_refresh: bool = False) -> None:
+        # A dbt run both updates data and changes schemas and has no way of rolling back so more closely maps to a SQLMesh forward-only plan
+        # TODO: if --full-refresh specified, mark incrementals as breaking instead of forward_only?
+
+        # TODO: we need to either convert DBT selector syntax to SQLMesh selector syntax
+        # or make the model selection engine configurable
+        select_models = None
+        if select:
+            if "," in select:
+                select_models = select.split(",")
+            else:
+                select_models = select.split(" ")
+
+        self.context.plan(
+            select_models=select_models,
+            no_auto_categorization=True,  # everything is breaking / foward-only
+            run=True,
+            no_diff=True,
+            no_prompts=True,
+            auto_apply=True,
+        )
+
+    @property
+    def console(self) -> DbtCliConsole:
+        console = self.context.console
+        from sqlmesh_dbt.console import DbtCliConsole
+
+        if not isinstance(console, DbtCliConsole):
+            raise ValueError(f"Expecting dbt cli console, got: {console}")
+
+        return console
+
+
+def create(
+    project_dir: t.Optional[Path] = None, profiles_dir: t.Optional[Path] = None, debug: bool = False
+) -> DbtOperations:
+    with Progress(transient=True) as progress:
+        # Indeterminate progress bar before SQLMesh import to provide feedback to the user that something is indeed happening
+        load_task_id = progress.add_task("Loading engine", total=None)
+
+        from sqlmesh import configure_logging
+        from sqlmesh.core.context import Context
+        from sqlmesh.dbt.loader import sqlmesh_config, DbtLoader
+        from sqlmesh.core.console import set_console
+        from sqlmesh_dbt.console import DbtCliConsole
+        from sqlmesh.utils.errors import SQLMeshError
+
+        configure_logging(force_debug=debug)
+        set_console(DbtCliConsole())
+
+        progress.update(load_task_id, description="Loading project", total=None)
+
+        # inject default start date if one is not specified to prevent the user from having to do anything
+        _inject_default_start_date(project_dir)
+
+        config = sqlmesh_config(
+            project_root=project_dir,
+            # do we want to use a local duckdb for state?
+            # warehouse state has a bunch of overhead to initialize, is slow for ongoing operations and will create tables that perhaps the user was not expecting
+            # on the other hand, local state is not portable
+            state_connection=None,
+        )
+
+        sqlmesh_context = Context(
+            config=config,
+            load=True,
+        )
+
+        # this helps things which want a default project-level start date, like the "effective from date" for forward-only plans
+        if not sqlmesh_context.config.model_defaults.start:
+            min_start_date = min(
+                (
+                    model.start
+                    for model in sqlmesh_context.models.values()
+                    if model.start is not None
+                ),
+                default=None,
+            )
+            sqlmesh_context.config.model_defaults.start = min_start_date
+
+        dbt_loader = sqlmesh_context._loaders[0]
+        if not isinstance(dbt_loader, DbtLoader):
+            raise SQLMeshError(f"Unexpected loader type: {type(dbt_loader)}")
+
+        # so that DbtOperations can query information from the DBT project files in order to invoke SQLMesh correctly
+        dbt_project = dbt_loader._projects[0]
+
+        return DbtOperations(sqlmesh_context, dbt_project)
+
+
+def _inject_default_start_date(project_dir: t.Optional[Path] = None) -> None:
+    """
+    SQLMesh needs a start date to as the starting point for calculating intervals on incremental models
+
+    Rather than forcing the user to update their config manually or having a default that is not saved between runs,
+    we can inject it automatically to the dbt_project.yml file
+    """
+    from sqlmesh.dbt.project import PROJECT_FILENAME, load_yaml
+    from sqlmesh.utils.yaml import dump
+    from sqlmesh.utils.date import yesterday_ds
+
+    project_yaml_path = (project_dir or Path.cwd()) / PROJECT_FILENAME
+    if project_yaml_path.exists():
+        loaded_project_file = load_yaml(project_yaml_path)
+        start_date_keys = ("start", "+start")
+        if "models" in loaded_project_file and all(
+            k not in loaded_project_file["models"] for k in start_date_keys
+        ):
+            loaded_project_file["models"]["+start"] = yesterday_ds()
+            # todo: this may format the file differently, is that acceptable?
+            with project_yaml_path.open("w") as f:
+                dump(loaded_project_file, f)

sqlmesh-0.209.1.dev12/tests/dbt/cli/conftest.py

@@ -0,0 +1,29 @@
+import typing as t
+from pathlib import Path
+import os
+import functools
+from click.testing import CliRunner, Result
+import pytest
+
+
+@pytest.fixture
+def jaffle_shop_duckdb(copy_to_temp_path: t.Callable[..., t.List[Path]]) -> t.Iterable[Path]:
+    fixture_path = Path(__file__).parent / "fixtures" / "jaffle_shop_duckdb"
+    assert fixture_path.exists()
+
+    current_path = os.getcwd()
+    output_path = copy_to_temp_path(paths=fixture_path)[0]
+
+    # so that we can invoke commands from the perspective of a user that is alrady in the correct directory
+    os.chdir(output_path)
+
+    yield output_path
+
+    os.chdir(current_path)
+
+
+@pytest.fixture
+def invoke_cli() -> t.Callable[..., Result]:
+    from sqlmesh_dbt.cli import dbt
+
+    return functools.partial(CliRunner().invoke, dbt)

sqlmesh-0.209.1.dev12/tests/dbt/cli/fixtures/jaffle_shop_duckdb/dbt_project.yml

@@ -0,0 +1,34 @@
+name: 'jaffle_shop'
+
+config-version: 2
+version: '0.1'
+
+profile: 'jaffle_shop'
+
+model-paths: ["models"]
+seed-paths: ["seeds"]
+test-paths: ["tests"]
+analysis-paths: ["analysis"]
+macro-paths: ["macros"]
+
+target-path: "target"
+clean-targets:
+    - "target"
+    - "dbt_modules"
+    - "logs"
+
+require-dbt-version: [">=1.0.0", "<2.0.0"]
+
+seeds: 
+  +docs:
+    node_color: '#cd7f32'
+
+models:
+  jaffle_shop:
+    +materialized: table
+    staging:
+      +materialized: view
+      +docs:
+        node_color: 'silver'
+    +docs:
+      node_color: 'gold'

sqlmesh-0.209.1.dev12/tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/customers.sql

@@ -0,0 +1,69 @@
+with customers as (
+
+    select * from {{ ref('stg_customers') }}
+
+),
+
+orders as (
+
+    select * from {{ ref('stg_orders') }}
+
+),
+
+payments as (
+
+    select * from {{ ref('stg_payments') }}
+
+),
+
+customer_orders as (
+
+        select
+        customer_id,
+
+        min(order_date) as first_order,
+        max(order_date) as most_recent_order,
+        count(order_id) as number_of_orders
+    from orders
+
+    group by customer_id
+
+),
+
+customer_payments as (
+
+    select
+        orders.customer_id,
+        sum(amount) as total_amount
+
+    from payments
+
+    left join orders on
+         payments.order_id = orders.order_id
+
+    group by orders.customer_id
+
+),
+
+final as (
+
+    select
+        customers.customer_id,
+        customers.first_name,
+        customers.last_name,
+        customer_orders.first_order,
+        customer_orders.most_recent_order,
+        customer_orders.number_of_orders,
+        customer_payments.total_amount as customer_lifetime_value
+
+    from customers
+
+    left join customer_orders
+        on customers.customer_id = customer_orders.customer_id
+
+    left join customer_payments
+        on  customers.customer_id = customer_payments.customer_id
+
+)
+
+select * from final

sqlmesh-0.209.1.dev12/tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/docs.md

@@ -0,0 +1,14 @@
+{% docs orders_status %}
+
+Orders can be one of the following statuses:
+
+| status         | description                                                                                                            |
+|----------------|------------------------------------------------------------------------------------------------------------------------|
+| placed         | The order has been placed but has not yet left the warehouse                                                           |
+| shipped        | The order has ben shipped to the customer and is currently in transit                                                  |
+| completed      | The order has been received by the customer                                                                            |
+| return_pending | The customer has indicated that they would like to return the order, but it has not yet been received at the warehouse |
+| returned       | The order has been returned by the customer and received at the warehouse                                              |
+
+
+{% enddocs %}

sqlmesh-0.209.1.dev12/tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/orders.sql

@@ -0,0 +1,56 @@
+{% set payment_methods = ['credit_card', 'coupon', 'bank_transfer', 'gift_card'] %}
+
+with orders as (
+
+    select * from {{ ref('stg_orders') }}
+
+),
+
+payments as (
+
+    select * from {{ ref('stg_payments') }}
+
+),
+
+order_payments as (
+
+    select
+        order_id,
+
+        {% for payment_method in payment_methods -%}
+        sum(case when payment_method = '{{ payment_method }}' then amount else 0 end) as {{ payment_method }}_amount,
+        {% endfor -%}
+
+        sum(amount) as total_amount
+
+    from payments
+
+    group by order_id
+
+),
+
+final as (
+
+    select
+        orders.order_id,
+        orders.customer_id,
+        orders.order_date,
+        orders.status,
+
+        {% for payment_method in payment_methods -%}
+
+        order_payments.{{ payment_method }}_amount,
+
+        {% endfor -%}
+
+        order_payments.total_amount as amount
+
+    from orders
+
+
+    left join order_payments
+        on orders.order_id = order_payments.order_id
+
+)
+
+select * from final

sqlmesh-0.209.1.dev12/tests/dbt/cli/fixtures/jaffle_shop_duckdb/models/overview.md

@@ -0,0 +1,11 @@
+{% docs __overview__ %}
+
+## Data Documentation for Jaffle Shop
+
+`jaffle_shop` is a fictional ecommerce store.
+
+This [dbt](https://www.getdbt.com/) project is for testing out code.
+
+The source code can be found [here](https://github.com/clrcrl/jaffle_shop).
+
+{% enddocs %}