model2data 0.3.0__tar.gz → 0.4.3__tar.gz

model2data-0.4.3/PKG-INFO

@@ -0,0 +1,285 @@
+Metadata-Version: 2.4
+Name: model2data
+Version: 0.4.3
+Summary: Generate analytics-ready datasets from DBML models
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: dbt-core>=1.5.0
+Requires-Dist: dbt-duckdb>=1.5.0
+Requires-Dist: faker>=37.12.0
+Requires-Dist: pandas>=2.3.3
+Requires-Dist: pyyaml>=6.0.3
+Requires-Dist: typer>=0.20.0
+Provides-Extra: postgres
+Requires-Dist: dbt-postgres>=1.5.0; extra == "postgres"
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
+Requires-Dist: ruff>=0.1.0; extra == "dev"
+Requires-Dist: ty>=0.0.4; extra == "dev"
+Requires-Dist: types-pyyaml; extra == "dev"
+Requires-Dist: poethepoet>=0.38.0; extra == "dev"
+Dynamic: license-file
+
+# model2data
+
+[![PyPI](https://img.shields.io/pypi/v/model2data)](https://pypi.org/project/model2data/)
+[![CI](https://github.com/JB-Analytica/model2data/actions/workflows/ci.yml/badge.svg)](https://github.com/JB-Analytica/model2data/actions/workflows/ci.yml)
+[![codecov](https://codecov.io/gh/JB-Analytica/model2data/branch/main/graph/badge.svg)](https://codecov.io/gh/JB-Analytica/model2data)
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+
+**Turn a data model into a running analytics stack in one command.**
+
+Give `model2data` a [DBML](https://dbml.dbdiagram.io/docs/) schema — hand-written or exported
+from an existing database — and it generates realistic, relationship-preserving synthetic data
+*and* a complete, runnable dbt project around it: seeds, staging models, sources, tests, and a
+DuckDB or Postgres profile. No sample data to hunt down, no dbt boilerplate to hand-write, no
+production data to risk exposing.
+
+```bash
+pip install model2data
+model2data --file examples/hackernews.dbml --rows 200 --seed 42
+cd dbt_hackernews && dbt seed && dbt run
+```
+
+That's a working analytics stack — real (synthetic) data, tested dbt models, queryable in
+DuckDB — from a schema file, in seconds:
+
+![model2data generating a project and running it with dbt](assets/demo.gif)
+
+---
+
+## Why this exists
+
+Analytics engineers hit the same wall constantly: you need realistic data to build or test a
+pipeline, but production data is off-limits (privacy, access, scale), and hand-rolling mock CSVs
+is tedious and doesn't scale past two tables. `model2data` closes that gap — from a schema
+definition to a seeded, tested dbt project you can actually run, with no database or production
+access required.
+
+- **Privacy-safe.** Nothing but a schema definition goes in; nothing but synthetic data comes out.
+- **Realistic, not random.** Column names are matched against ~35 common patterns — `email`,
+  `first_name`, `city`, `phone`, `company`, ... — so a column called `email` gets real-looking
+  emails, not `Lorem ipsum` text.
+- **Relationship-preserving.** Foreign keys resolve to real parent rows; tables are generated in
+  dependency order.
+- **Deterministic.** Pass `--seed` and the same schema always produces the same data — safe to
+  commit fixtures, safe to diff across CI runs.
+- **A real dbt project, not just CSVs.** Seeds, staging models, sources, schema tests, and a
+  ready-to-use profile — the thing you'd otherwise spend an afternoon scaffolding by hand.
+
+## Who is model2data for?
+
+- **Analytics engineers** — generate realistic datasets and a working dbt project without
+  waiting on production access.
+- **Data engineers** — produce deterministic test data from an existing schema for pipeline and
+  migration testing.
+- **Software & data teams** — prototype integrations and analytics workflows without exposing
+  production data.
+- **Consultants & architects** — spin up realistic environments for demos, workshops, and
+  architecture validation in minutes, not hours.
+
+## How it works
+
+```mermaid
+flowchart LR
+    subgraph input [" "]
+        A["📄 DBML schema"]
+    end
+
+    subgraph m2d ["model2data"]
+        direction LR
+        B["Parse\ntables, columns,\nrelationships"] --> C["Generate\nFaker + name-aware\ninference, FK-aware"]
+        C --> D["Scaffold\nseeds · staging models\ntests · profile"]
+    end
+
+    subgraph output ["Generated dbt project"]
+        direction TB
+        E["seeds/*.csv"]
+        F["models/staging/*.sql + *.yml"]
+        G["profiles.yml\n(DuckDB or Postgres)"]
+    end
+
+    A --> B
+    D --> E
+    D --> F
+    D --> G
+    E & F & G --> H["dbt seed && dbt run"]
+    H --> I[("Analytics-ready\ndataset")]
+
+    classDef m2dStyle fill:#0A3866,stroke:#2196F0,color:#F6F8FB
+    classDef outStyle fill:#182333,stroke:#A8C9EE,color:#F6F8FB
+    classDef endStyle fill:#FA9306,stroke:#FA9306,color:#182333
+    class B,C,D m2dStyle
+    class E,F,G outStyle
+    class H,I endStyle
+```
+
+1. **Parse.** Reads tables, columns, types, and `Ref` relationships from a DBML file.
+2. **Generate.** Produces synthetic values per column — typed generation for known SQL types
+   (int, date, timestamp, ...), name-aware inference for everything else (`email`, `phone`,
+   `city`, ...), foreign keys resolved against already-generated parent rows.
+3. **Scaffold.** Writes a complete dbt project around that data: CSV seeds, staging models with
+   `source`/`not_null`/`unique`/`relationships` tests, `accepted_values` tests for DBML
+   `Enum`-typed columns, singular SQL tests for composite primary/unique keys, table and column
+   `description:` fields pulled from DBML notes, and a profile for DuckDB (zero-config,
+   file-based) or Postgres.
+
+---
+
+## Installation
+
+```bash
+pip install model2data
+```
+
+---
+
+## Quick start
+
+We provide an example Hacker News dataset in `examples/hackernews.dbml`.
+
+Generate a project with synthetic data:
+
+```bash
+model2data --file examples/hackernews.dbml --rows 200 --seed 42
+```
+
+This creates a `dbt_hackernews/` folder with your data and dbt setup.
+
+Run dbt to load and transform the data:
+
+```bash
+cd dbt_hackernews
+dbt deps
+dbt seed
+dbt run
+```
+
+Your analytics-ready dataset is now in DuckDB!
+
+To target Postgres instead, install the extra and pass `--adapter postgres`:
+
+```bash
+pip install "model2data[postgres]"
+model2data --file examples/hackernews.dbml --rows 200 --seed 42 --adapter postgres
+```
+
+Connection details are read from environment variables (`MODEL2DATA_PG_HOST`, `MODEL2DATA_PG_PORT`, `MODEL2DATA_PG_USER`, `MODEL2DATA_PG_PASSWORD`, `MODEL2DATA_PG_DATABASE`), defaulting to `localhost:5432` with a `postgres`/`postgres` user for local development.
+
+After generation, the CLI prints a short summary — tables and rows generated, relationships found in the DBML, and any columns that fell back to generic placeholder text because neither their type nor name could be matched.
+
+Pass `--unit-tests` to also generate deterministic dbt unit test fixtures (`models/staging/ut_stg_<table>.yml`) from the actually-generated seed rows:
+
+```bash
+model2data --file examples/hackernews.dbml --rows 200 --seed 42 --unit-tests
+```
+
+This targets dbt-core's native unit testing feature, which requires **dbt-core >= 1.8**. Since this project only requires `dbt-core>=1.5.0` by default, unit test generation is opt-in — leave the flag off if your dbt-core version is older.
+
+---
+
+## Generated dbt project structure
+
+The generated dbt project includes:
+
+```
+dbt_{project_name}/
+├── seeds/
+│   └── raw/
+│       ├── table1.csv
+│       └── table2.csv
+├── models/
+│   └── staging/
+│       ├── __sources.yml
+│       ├── stg_table1.sql
+│       ├── stg_table1.yml
+│       ├── ut_stg_table1.yml  # only with --unit-tests
+│       └── ...
+├── data-tests/
+│   └── unique_combination_stg_table1_col_a_col_b.sql  # only for composite pk/unique keys
+├── macros/
+│   └── generate_schema_name.sql
+├── dbt_project.yml
+├── profiles.yml  # DuckDB or Postgres config, depending on --adapter
+└── {project_name}_profile.duckdb  # DuckDB adapter only
+```
+
+- **Seeds**: CSV files with generated synthetic data.
+- **Staging Models**: Basic dbt models that load from seeds.
+- **Sources & Tests**: YAML configs defining sources and column tests (`not_null`, `unique`,
+  `relationships`, and `accepted_values` for DBML `Enum`-typed columns). Table and column
+  `Note` text from the DBML becomes `description:` fields.
+- **Composite key tests**: Composite primary/unique keys declared in an `indexes { }` block get
+  a singular SQL test under `data-tests/`, dbt's configured `test-paths`.
+- **Profiles**: Pre-configured for DuckDB (file-based) or Postgres (via env vars), with schema handling.
+- **Unit tests** (opt-in via `--unit-tests`): `models/staging/ut_stg_<table>.yml` fixtures built
+  from real generated rows, co-located with each staging model so dbt (which only parses unit
+  tests from `model-paths`) picks them up. Requires dbt-core >= 1.8.
+
+---
+
+## Design decisions / non-goals
+
+- **DuckDB Default**: Chosen for its zero-config, file-based nature, making it easy to get started without database setup. Postgres is supported via `--adapter postgres`; other adapters can be configured manually.
+- **dbt Integration**: Leverages dbt's transformation capabilities for a familiar workflow in analytics engineering.
+- **Synthetic Data**: Uses deterministic generation for reproducibility; not intended for production use or as a replacement for real data.
+- **Non-goals**: This is not a data migration tool, ETL pipeline, or real-time data generator. It focuses on static, synthetic datasets for testing and prototyping.
+
+---
+
+## Limitations
+
+- Supports basic DBML features; complex constraints or advanced SQL types may not be fully handled.
+- Synthetic data generation is heuristic-based and may not perfectly mimic real-world distributions or edge cases.
+- DuckDB and Postgres are supported today; other databases require manual profile adjustments.
+- No support for incremental models or advanced dbt features in generated projects.
+
+---
+
+## Roadmap
+
+- [x] Postgres adapter support (`--adapter postgres`)
+- [x] Name-aware synthetic data (email, name, address, phone, etc. instead of generic text)
+- [x] Post-run generation summary (tables, rows, relationships, unmapped columns)
+- [x] DBML `Enum` support, real table/column notes as dbt descriptions, composite keys from
+      `indexes { }`, `default:` values, and opt-in deterministic dbt unit test scaffolding
+      (`--unit-tests`)
+- [ ] Additional database adapters (e.g., Snowflake, BigQuery).
+- [ ] Enhanced data type handling and custom generators.
+- [ ] Improved schema exploration and developer tooling.
+
+---
+
+## Contributing
+
+We welcome contributions!
+
+- Open issues for bugs or feature requests.
+- Submit PRs to add new DBML examples, custom data generators, or improvements.
+- Ensure all new features include tests if possible.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines, and [DEVELOPMENT.md](DEVELOPMENT.md) for the local dev setup and release process.
+
+## Code of Conduct
+
+Please read our [Code of Conduct](CODE_OF_CONDUCT.md) to understand our community standards.
+
+---
+
+## License
+
+MIT License. See LICENSE for details.
+
+---
+
+<p align="center">
+  <a href="https://www.jbanalytica.com">
+    <img src="assets/jba-icon-dark-bg.svg" alt="JB Analytica" height="40">
+  </a>
+  <br>
+  Built and maintained by <a href="https://www.jbanalytica.com"><strong>JB Analytica</strong></a> —
+  Data & Analytics Engineering · Data Platform Architecture · Modern BI.
+</p>

model2data-0.4.3/README.md

@@ -0,0 +1,260 @@
+# model2data
+
+[![PyPI](https://img.shields.io/pypi/v/model2data)](https://pypi.org/project/model2data/)
+[![CI](https://github.com/JB-Analytica/model2data/actions/workflows/ci.yml/badge.svg)](https://github.com/JB-Analytica/model2data/actions/workflows/ci.yml)
+[![codecov](https://codecov.io/gh/JB-Analytica/model2data/branch/main/graph/badge.svg)](https://codecov.io/gh/JB-Analytica/model2data)
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
+
+**Turn a data model into a running analytics stack in one command.**
+
+Give `model2data` a [DBML](https://dbml.dbdiagram.io/docs/) schema — hand-written or exported
+from an existing database — and it generates realistic, relationship-preserving synthetic data
+*and* a complete, runnable dbt project around it: seeds, staging models, sources, tests, and a
+DuckDB or Postgres profile. No sample data to hunt down, no dbt boilerplate to hand-write, no
+production data to risk exposing.
+
+```bash
+pip install model2data
+model2data --file examples/hackernews.dbml --rows 200 --seed 42
+cd dbt_hackernews && dbt seed && dbt run
+```
+
+That's a working analytics stack — real (synthetic) data, tested dbt models, queryable in
+DuckDB — from a schema file, in seconds:
+
+![model2data generating a project and running it with dbt](assets/demo.gif)
+
+---
+
+## Why this exists
+
+Analytics engineers hit the same wall constantly: you need realistic data to build or test a
+pipeline, but production data is off-limits (privacy, access, scale), and hand-rolling mock CSVs
+is tedious and doesn't scale past two tables. `model2data` closes that gap — from a schema
+definition to a seeded, tested dbt project you can actually run, with no database or production
+access required.
+
+- **Privacy-safe.** Nothing but a schema definition goes in; nothing but synthetic data comes out.
+- **Realistic, not random.** Column names are matched against ~35 common patterns — `email`,
+  `first_name`, `city`, `phone`, `company`, ... — so a column called `email` gets real-looking
+  emails, not `Lorem ipsum` text.
+- **Relationship-preserving.** Foreign keys resolve to real parent rows; tables are generated in
+  dependency order.
+- **Deterministic.** Pass `--seed` and the same schema always produces the same data — safe to
+  commit fixtures, safe to diff across CI runs.
+- **A real dbt project, not just CSVs.** Seeds, staging models, sources, schema tests, and a
+  ready-to-use profile — the thing you'd otherwise spend an afternoon scaffolding by hand.
+
+## Who is model2data for?
+
+- **Analytics engineers** — generate realistic datasets and a working dbt project without
+  waiting on production access.
+- **Data engineers** — produce deterministic test data from an existing schema for pipeline and
+  migration testing.
+- **Software & data teams** — prototype integrations and analytics workflows without exposing
+  production data.
+- **Consultants & architects** — spin up realistic environments for demos, workshops, and
+  architecture validation in minutes, not hours.
+
+## How it works
+
+```mermaid
+flowchart LR
+    subgraph input [" "]
+        A["📄 DBML schema"]
+    end
+
+    subgraph m2d ["model2data"]
+        direction LR
+        B["Parse\ntables, columns,\nrelationships"] --> C["Generate\nFaker + name-aware\ninference, FK-aware"]
+        C --> D["Scaffold\nseeds · staging models\ntests · profile"]
+    end
+
+    subgraph output ["Generated dbt project"]
+        direction TB
+        E["seeds/*.csv"]
+        F["models/staging/*.sql + *.yml"]
+        G["profiles.yml\n(DuckDB or Postgres)"]
+    end
+
+    A --> B
+    D --> E
+    D --> F
+    D --> G
+    E & F & G --> H["dbt seed && dbt run"]
+    H --> I[("Analytics-ready\ndataset")]
+
+    classDef m2dStyle fill:#0A3866,stroke:#2196F0,color:#F6F8FB
+    classDef outStyle fill:#182333,stroke:#A8C9EE,color:#F6F8FB
+    classDef endStyle fill:#FA9306,stroke:#FA9306,color:#182333
+    class B,C,D m2dStyle
+    class E,F,G outStyle
+    class H,I endStyle
+```
+
+1. **Parse.** Reads tables, columns, types, and `Ref` relationships from a DBML file.
+2. **Generate.** Produces synthetic values per column — typed generation for known SQL types
+   (int, date, timestamp, ...), name-aware inference for everything else (`email`, `phone`,
+   `city`, ...), foreign keys resolved against already-generated parent rows.
+3. **Scaffold.** Writes a complete dbt project around that data: CSV seeds, staging models with
+   `source`/`not_null`/`unique`/`relationships` tests, `accepted_values` tests for DBML
+   `Enum`-typed columns, singular SQL tests for composite primary/unique keys, table and column
+   `description:` fields pulled from DBML notes, and a profile for DuckDB (zero-config,
+   file-based) or Postgres.
+
+---
+
+## Installation
+
+```bash
+pip install model2data
+```
+
+---
+
+## Quick start
+
+We provide an example Hacker News dataset in `examples/hackernews.dbml`.
+
+Generate a project with synthetic data:
+
+```bash
+model2data --file examples/hackernews.dbml --rows 200 --seed 42
+```
+
+This creates a `dbt_hackernews/` folder with your data and dbt setup.
+
+Run dbt to load and transform the data:
+
+```bash
+cd dbt_hackernews
+dbt deps
+dbt seed
+dbt run
+```
+
+Your analytics-ready dataset is now in DuckDB!
+
+To target Postgres instead, install the extra and pass `--adapter postgres`:
+
+```bash
+pip install "model2data[postgres]"
+model2data --file examples/hackernews.dbml --rows 200 --seed 42 --adapter postgres
+```
+
+Connection details are read from environment variables (`MODEL2DATA_PG_HOST`, `MODEL2DATA_PG_PORT`, `MODEL2DATA_PG_USER`, `MODEL2DATA_PG_PASSWORD`, `MODEL2DATA_PG_DATABASE`), defaulting to `localhost:5432` with a `postgres`/`postgres` user for local development.
+
+After generation, the CLI prints a short summary — tables and rows generated, relationships found in the DBML, and any columns that fell back to generic placeholder text because neither their type nor name could be matched.
+
+Pass `--unit-tests` to also generate deterministic dbt unit test fixtures (`models/staging/ut_stg_<table>.yml`) from the actually-generated seed rows:
+
+```bash
+model2data --file examples/hackernews.dbml --rows 200 --seed 42 --unit-tests
+```
+
+This targets dbt-core's native unit testing feature, which requires **dbt-core >= 1.8**. Since this project only requires `dbt-core>=1.5.0` by default, unit test generation is opt-in — leave the flag off if your dbt-core version is older.
+
+---
+
+## Generated dbt project structure
+
+The generated dbt project includes:
+
+```
+dbt_{project_name}/
+├── seeds/
+│   └── raw/
+│       ├── table1.csv
+│       └── table2.csv
+├── models/
+│   └── staging/
+│       ├── __sources.yml
+│       ├── stg_table1.sql
+│       ├── stg_table1.yml
+│       ├── ut_stg_table1.yml  # only with --unit-tests
+│       └── ...
+├── data-tests/
+│   └── unique_combination_stg_table1_col_a_col_b.sql  # only for composite pk/unique keys
+├── macros/
+│   └── generate_schema_name.sql
+├── dbt_project.yml
+├── profiles.yml  # DuckDB or Postgres config, depending on --adapter
+└── {project_name}_profile.duckdb  # DuckDB adapter only
+```
+
+- **Seeds**: CSV files with generated synthetic data.
+- **Staging Models**: Basic dbt models that load from seeds.
+- **Sources & Tests**: YAML configs defining sources and column tests (`not_null`, `unique`,
+  `relationships`, and `accepted_values` for DBML `Enum`-typed columns). Table and column
+  `Note` text from the DBML becomes `description:` fields.
+- **Composite key tests**: Composite primary/unique keys declared in an `indexes { }` block get
+  a singular SQL test under `data-tests/`, dbt's configured `test-paths`.
+- **Profiles**: Pre-configured for DuckDB (file-based) or Postgres (via env vars), with schema handling.
+- **Unit tests** (opt-in via `--unit-tests`): `models/staging/ut_stg_<table>.yml` fixtures built
+  from real generated rows, co-located with each staging model so dbt (which only parses unit
+  tests from `model-paths`) picks them up. Requires dbt-core >= 1.8.
+
+---
+
+## Design decisions / non-goals
+
+- **DuckDB Default**: Chosen for its zero-config, file-based nature, making it easy to get started without database setup. Postgres is supported via `--adapter postgres`; other adapters can be configured manually.
+- **dbt Integration**: Leverages dbt's transformation capabilities for a familiar workflow in analytics engineering.
+- **Synthetic Data**: Uses deterministic generation for reproducibility; not intended for production use or as a replacement for real data.
+- **Non-goals**: This is not a data migration tool, ETL pipeline, or real-time data generator. It focuses on static, synthetic datasets for testing and prototyping.
+
+---
+
+## Limitations
+
+- Supports basic DBML features; complex constraints or advanced SQL types may not be fully handled.
+- Synthetic data generation is heuristic-based and may not perfectly mimic real-world distributions or edge cases.
+- DuckDB and Postgres are supported today; other databases require manual profile adjustments.
+- No support for incremental models or advanced dbt features in generated projects.
+
+---
+
+## Roadmap
+
+- [x] Postgres adapter support (`--adapter postgres`)
+- [x] Name-aware synthetic data (email, name, address, phone, etc. instead of generic text)
+- [x] Post-run generation summary (tables, rows, relationships, unmapped columns)
+- [x] DBML `Enum` support, real table/column notes as dbt descriptions, composite keys from
+      `indexes { }`, `default:` values, and opt-in deterministic dbt unit test scaffolding
+      (`--unit-tests`)
+- [ ] Additional database adapters (e.g., Snowflake, BigQuery).
+- [ ] Enhanced data type handling and custom generators.
+- [ ] Improved schema exploration and developer tooling.
+
+---
+
+## Contributing
+
+We welcome contributions!
+
+- Open issues for bugs or feature requests.
+- Submit PRs to add new DBML examples, custom data generators, or improvements.
+- Ensure all new features include tests if possible.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines, and [DEVELOPMENT.md](DEVELOPMENT.md) for the local dev setup and release process.
+
+## Code of Conduct
+
+Please read our [Code of Conduct](CODE_OF_CONDUCT.md) to understand our community standards.
+
+---
+
+## License
+
+MIT License. See LICENSE for details.
+
+---
+
+<p align="center">
+  <a href="https://www.jbanalytica.com">
+    <img src="assets/jba-icon-dark-bg.svg" alt="JB Analytica" height="40">
+  </a>
+  <br>
+  Built and maintained by <a href="https://www.jbanalytica.com"><strong>JB Analytica</strong></a> —
+  Data & Analytics Engineering · Data Platform Architecture · Modern BI.
+</p>

{model2data-0.3.0 → model2data-0.4.3}/model2data/cli.py

@@ -11,7 +11,7 @@ from model2data.dbt.project import (
     create_project_scaffold,
     create_staging_models,
 )
-from model2data.dbt.tests import generate_dbt_yml
+from model2data.dbt.tests import generate_dbt_yml, generate_unit_tests
 from model2data.generate.core import generate_data_from_dbml
 from model2data.generate.faker import get_unmapped_columns, reset_stats
 from model2data.parse.dbml import parse_dbml
@@ -76,6 +76,14 @@ def main(
         "-a",
         help=f"dbt warehouse adapter to target. One of: {', '.join(SUPPORTED_ADAPTERS)}.",
     ),
+    unit_tests: bool = typer.Option(
+        False,
+        "--unit-tests",
+        help=(
+            "Also generate deterministic dbt unit test fixtures (models/staging/ut_stg_*.yml) "
+            "from the generated seed rows. Requires dbt-core >= 1.8 to run."
+        ),
+    ),
 ):
     """
     Generate synthetic data and a dbt project from a DBML model.
@@ -152,6 +160,10 @@ def main(
     typer.echo("🧪 Generating dbt yml with tests...")
     generate_dbt_yml(dest, tables, refs, project_name)
 
+    if unit_tests:
+        typer.echo("🔬 Generating dbt unit test fixtures (requires dbt-core >= 1.8)...")
+        generate_unit_tests(dest, tables, generated_tables)
+
     typer.echo(f"🪪 Ensuring dbt profile exists ({adapter})...")
     create_profiles_yml(dest, profile_name, adapter=adapter)
 

{model2data-0.3.0 → model2data-0.4.3}/model2data/dbt/project.py

@@ -13,7 +13,7 @@ def create_project_scaffold(dest: Path, project_name: str, profile_name: str) ->
     (dest / "seeds" / "raw").mkdir(parents=True, exist_ok=True)
     (dest / "analysis").mkdir(exist_ok=True)
     (dest / "macros").mkdir(exist_ok=True)
-    (dest / "tests").mkdir(exist_ok=True)
+    (dest / "data-tests").mkdir(exist_ok=True)
     (dest / "snapshots").mkdir(exist_ok=True)
 
     # dbt_project.yml