trellis-datamodel 0.1.2__tar.gz

trellis_datamodel-0.1.2/PKG-INFO

@@ -0,0 +1,298 @@
+Metadata-Version: 2.4
+Name: trellis-datamodel
+Version: 0.1.2
+Summary: Visual data model editor for dbt projects
+Author: Tim Hiebenthal
+Project-URL: Homepage, https://github.com/timhiebenthal/trellis-datamodel
+Project-URL: Repository, https://github.com/timhiebenthal/trellis-datamodel
+Project-URL: Issues, https://github.com/timhiebenthal/trellis-datamodel/issues
+Keywords: dbt,data-modeling,erd,data-engineering,analytics-engineering,visualization,schema
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+Requires-Dist: dbt-core<2.0,>=1.6
+Requires-Dist: fastapi>=0.121.3
+Requires-Dist: python-dotenv>=1.2.1
+Requires-Dist: pyyaml>=6.0.3
+Requires-Dist: ruamel.yaml>=0.18.0
+Requires-Dist: typer>=0.9.0
+Requires-Dist: uvicorn>=0.38.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0.0; extra == "dev"
+Requires-Dist: httpx>=0.27.0; extra == "dev"
+Provides-Extra: examples
+Requires-Dist: dbt-duckdb==1.10; extra == "examples"
+Requires-Dist: duckdb>=1.4.2; extra == "examples"
+Requires-Dist: marimo>=0.18.0; extra == "examples"
+Requires-Dist: nba-api>=1.11.3; extra == "examples"
+Requires-Dist: pandas>=2.3.3; extra == "examples"
+Requires-Dist: tqdm>=4.67.1; extra == "examples"
+
+# Trellis Data
+
+A local-first tool to bridge Conceptual Data Modeling, Logical Data Modeling and the physical Implementation (currently with dbt-core).
+
+## Motivation
+
+**Current workflow pains:**
+- ERD diagrams live in separate tools (Lucidchart, draw.io) and quickly become stale or unreadable for large projects
+- Data transformations are done isolated from the conceptual data model.
+- No single view connecting business concepts to logical schema
+- Stakeholders can't easily understand model structure without technical context
+
+**How Trellis helps:**
+- Visual data model that stays in sync — reads directly from `manifest.json` / `catalog.json`
+- Sketch entities and with their fields and auto-generate schema.yml's for dbt
+- Draw relationships on canvas → auto-generates dbt `relationships` tests
+- Two views: **Conceptual** (entity names, descriptions) and **Logical** (columns, types, materializations) to jump between high-level architect and execution-view.
+
+**Two Ways of getting started** 
+- Greenfield: draft entities and fields before writing SQL, then sync to dbt YAML  
+- Brownfield: document your existing data model by loading existing dbt models and utilize relationship tests to infer links
+
+## Prerequisites
+- **Node.js 22+ (or 20.19+) & npm**  
+  - Recommended: Use [nvm](https://github.com/nvm-sh/nvm) to install a compatible version (e.g., `nvm install 22`).
+  - Note: System packages (`apt-get`) may be too old for the frontend dependencies.
+  - A `.nvmrc` file is included; run `nvm use` to switch to the correct version automatically.
+- **Python 3.12+ & [uv](https://github.com/astral-sh/uv)**  
+  - Install uv via `curl -LsSf https://astral.sh/uv/install.sh | sh` and ensure it’s on your `$PATH`.
+- **Make** (optional) for convenience targets defined in the `Makefile`.
+
+## Installation
+
+### Install from PyPI
+
+```bash
+pip install trellis-datamodel
+# or with uv
+uv pip install trellis-datamodel
+```
+
+### Install from Source (Development)
+
+```bash
+# Clone the repository
+git clone https://github.com/yourorg/trellis-datamodel.git
+cd trellis-datamodel
+
+# Install in editable mode
+pip install -e .
+# or with uv
+uv pip install -e .
+```
+
+## Quick Start
+
+1. **Navigate to your dbt project directory**
+   ```bash
+   cd /path/to/your/dbt-project
+   ```
+
+2. **Initialize configuration**
+   ```bash
+   trellis init
+   ```
+   This creates a `trellis.yml` file. Edit it to point to your dbt manifest and catalog locations.
+
+3. **Start the server**
+   ```bash
+   trellis run
+   ```
+
+   The server will start on **http://localhost:8089** and automatically open your browser.
+
+## Development Setup
+
+For local development with hot reload:
+
+### Install Dependencies
+Run these once per machine (or when dependencies change).
+
+1. **Backend**
+   ```bash
+   uv sync
+   ```
+2. **Frontend**
+   ```bash
+   cd frontend
+   npm install
+   ```
+
+**Terminal 1 – Backend**
+```bash
+make backend
+# or
+uv run trellis run
+```
+Backend serves the API at http://localhost:8089.
+
+**Terminal 2 – Frontend**
+```bash
+make frontend
+# or
+cd frontend && npm run dev
+```
+Frontend runs at http://localhost:5173 (for development with hot reload).
+
+## Building for Distribution
+
+To build the package with bundled frontend:
+
+```bash
+make build-package
+```
+
+This will:
+1. Build the frontend (`npm run build`)
+2. Copy static files to `trellis_datamodel/static/`
+3. Build the Python wheel (`uv build`)
+
+The wheel will be in `dist/` and can be installed with `pip install dist/trellis_datamodel-*.whl`.
+
+## CLI Options
+
+```bash
+trellis run [OPTIONS]
+
+Options:
+  --port, -p INTEGER    Port to run the server on [default: 8089]
+  --config, -c TEXT     Path to config file (trellis.yml or config.yml)
+  --no-browser          Don't open browser automatically
+  --help                Show help message
+```
+
+## dbt Metadata
+- Generate `manifest.json` and `catalog.json` by running `dbt docs generate` in your dbt project.
+- The UI reads these artifacts to power the ERD modeller.
+- Without these artifacts, the UI loads but shows no dbt models.
+
+## Configuration
+
+Run `trellis init` to create a starter `trellis.yml` file in your project.
+
+Options:
+
+- `framework`: Transformation framework to use. Currently supported: `dbt-core`. Future: `dbt-fusion`, `sqlmesh`, `bruin`, `pydantic`. Defaults to `dbt-core`.
+- `dbt_project_path`: Path to your dbt project directory (relative to `config.yml` or absolute). **Required**.
+- `dbt_manifest_path`: Path to `manifest.json` (relative to `dbt_project_path` or absolute). Defaults to `target/manifest.json`.
+- `dbt_catalog_path`: Path to `catalog.json` (relative to `dbt_project_path` or absolute). Defaults to `target/catalog.json`.
+- `data_model_file`: Path where the data model YAML will be saved (relative to `dbt_project_path` or absolute). Defaults to `data_model.yml`.
+- `dbt_model_paths`: List of path patterns to filter which dbt models are shown (e.g., `["3_core"]`). If empty, all models are included.
+
+**Example `trellis.yml`:**
+```yaml
+framework: dbt-core
+dbt_project_path: "./dbt_built"
+dbt_manifest_path: "target/manifest.json"
+dbt_catalog_path: "target/catalog.json"
+data_model_file: "data_model.yml"
+dbt_model_paths:
+  - "3_core"
+```
+
+
+## Testing
+
+### Frontend
+**Testing Libraries:**
+The following testing libraries are defined in `package.json` under `devDependencies` and are automatically installed when you run `npm install`:
+- [Vitest](https://vitest.dev/) (Unit testing)
+- [Playwright](https://playwright.dev/) (End-to-End testing)
+- [Testing Library](https://testing-library.com/) (DOM & Svelte testing utilities)
+- [jsdom](https://github.com/jsdom/jsdom) (DOM environment)
+
+> **Playwright system dependencies (Ubuntu/WSL2)**
+>
+> The browsers downloaded by Playwright need a handful of native libraries. Install them before running `npm run test:e2e`:
+>
+> ```bash
+> sudo apt-get update && sudo apt-get install -y \
+>   libxcursor1 libxdamage1 libgtk-3-0 libpangocairo-1.0-0 libpango-1.0-0 \
+>   libatk1.0-0 libcairo-gobject2 libcairo2 libgdk-pixbuf-2.0-0 libasound2 \
+>   libnspr4 libnss3 libgbm1 libgles2-mesa libgtk-4-1 libgraphene-1.0-0 \
+>   libxslt1.1 libwoff2dec0 libvpx7 libevent-2.1-7 libopus0 \
+>   libgstallocators-1.0-0 libgstapp-1.0-0 libgstpbutils-1.0-0 libgstaudio-1.0-0 \
+>   libgsttag-1.0-0 libgstvideo-1.0-0 libgstgl-1.0-0 libgstcodecparsers-1.0-0 \
+>   libgstfft-1.0-0 libflite1 libflite1-plugins libwebpdemux2 libavif13 \
+>   libharfbuzz-icu0 libwebpmux3 libenchant-2-2 libsecret-1-0 libhyphen0 \
+>   libwayland-server0 libmanette-0.2-0 libx264-163
+> ```
+
+**Running Tests:**
+
+The test suite has multiple levels to catch different types of issues:
+
+```bash
+cd frontend
+
+# Quick smoke test (catches 500 errors, runtime crashes, ESM issues)
+# Fastest way to verify the app loads without errors
+npm run test:smoke
+
+# TypeScript/compilation check
+npm run check
+
+# Unit tests
+npm run test:unit
+
+# E2E tests (includes smoke test + full test suite)
+# Note: Requires backend running with test data (see Test Data Isolation below)
+npm run test:e2e
+
+# Run all tests (check + smoke + unit + e2e)
+npm run test
+```
+
+**Test Levels:**
+1. **`npm run check`** - TypeScript compilation errors
+2. **`npm run test:smoke`** - Runtime errors (500s, console errors, ESM issues) - **catches app crashes**
+3. **`npm run test:unit`** - Unit tests with Vitest
+4. **`npm run test:e2e`** - Full E2E tests with Playwright
+
+**Using Makefile:**
+```bash
+# From project root
+make test-smoke     # Quick smoke test
+make test-check     # TypeScript check
+make test-unit      # Unit tests
+make test-e2e       # E2E tests (auto-starts backend with test data)
+make test-all       # All tests
+```
+
+**Test Data Isolation:**
+E2E tests use a separate test data file (`frontend/tests/test_data_model.yml`) to avoid polluting your production data model. **Playwright automatically starts the backend** with the correct environment variable, so you don't need to manage it manually.
+
+```bash
+# Just run E2E tests - backend starts automatically with test data
+make test-e2e
+# OR:
+# cd frontend && npm run test:e2e
+```
+
+The test data file is automatically cleaned before and after test runs via Playwright's `globalSetup` and `globalTeardown`. Your production `data_model.yml` remains untouched.
+
+### Backend
+**Testing Libraries:**
+The following testing libraries are defined in `pyproject.toml` under `[project.optional-dependencies]` in the `dev` group:
+- [pytest](https://docs.pytest.org/) (Testing framework)
+- [httpx](https://www.python-httpx.org/) (Async HTTP client for API testing)
+
+**Installation:**
+Unlike `npm`, `uv sync` does not install optional dependencies by default. To include the testing libraries, run:
+```bash
+cd backend
+uv sync --extra dev
+```
+
+**Running Tests:**
+```bash
+cd backend
+uv run pytest
+```

trellis_datamodel-0.1.2/README.md

@@ -0,0 +1,262 @@
+# Trellis Data
+
+A local-first tool to bridge Conceptual Data Modeling, Logical Data Modeling and the physical Implementation (currently with dbt-core).
+
+## Motivation
+
+**Current workflow pains:**
+- ERD diagrams live in separate tools (Lucidchart, draw.io) and quickly become stale or unreadable for large projects
+- Data transformations are done isolated from the conceptual data model.
+- No single view connecting business concepts to logical schema
+- Stakeholders can't easily understand model structure without technical context
+
+**How Trellis helps:**
+- Visual data model that stays in sync — reads directly from `manifest.json` / `catalog.json`
+- Sketch entities and with their fields and auto-generate schema.yml's for dbt
+- Draw relationships on canvas → auto-generates dbt `relationships` tests
+- Two views: **Conceptual** (entity names, descriptions) and **Logical** (columns, types, materializations) to jump between high-level architect and execution-view.
+
+**Two Ways of getting started** 
+- Greenfield: draft entities and fields before writing SQL, then sync to dbt YAML  
+- Brownfield: document your existing data model by loading existing dbt models and utilize relationship tests to infer links
+
+## Prerequisites
+- **Node.js 22+ (or 20.19+) & npm**  
+  - Recommended: Use [nvm](https://github.com/nvm-sh/nvm) to install a compatible version (e.g., `nvm install 22`).
+  - Note: System packages (`apt-get`) may be too old for the frontend dependencies.
+  - A `.nvmrc` file is included; run `nvm use` to switch to the correct version automatically.
+- **Python 3.12+ & [uv](https://github.com/astral-sh/uv)**  
+  - Install uv via `curl -LsSf https://astral.sh/uv/install.sh | sh` and ensure it’s on your `$PATH`.
+- **Make** (optional) for convenience targets defined in the `Makefile`.
+
+## Installation
+
+### Install from PyPI
+
+```bash
+pip install trellis-datamodel
+# or with uv
+uv pip install trellis-datamodel
+```
+
+### Install from Source (Development)
+
+```bash
+# Clone the repository
+git clone https://github.com/yourorg/trellis-datamodel.git
+cd trellis-datamodel
+
+# Install in editable mode
+pip install -e .
+# or with uv
+uv pip install -e .
+```
+
+## Quick Start
+
+1. **Navigate to your dbt project directory**
+   ```bash
+   cd /path/to/your/dbt-project
+   ```
+
+2. **Initialize configuration**
+   ```bash
+   trellis init
+   ```
+   This creates a `trellis.yml` file. Edit it to point to your dbt manifest and catalog locations.
+
+3. **Start the server**
+   ```bash
+   trellis run
+   ```
+
+   The server will start on **http://localhost:8089** and automatically open your browser.
+
+## Development Setup
+
+For local development with hot reload:
+
+### Install Dependencies
+Run these once per machine (or when dependencies change).
+
+1. **Backend**
+   ```bash
+   uv sync
+   ```
+2. **Frontend**
+   ```bash
+   cd frontend
+   npm install
+   ```
+
+**Terminal 1 – Backend**
+```bash
+make backend
+# or
+uv run trellis run
+```
+Backend serves the API at http://localhost:8089.
+
+**Terminal 2 – Frontend**
+```bash
+make frontend
+# or
+cd frontend && npm run dev
+```
+Frontend runs at http://localhost:5173 (for development with hot reload).
+
+## Building for Distribution
+
+To build the package with bundled frontend:
+
+```bash
+make build-package
+```
+
+This will:
+1. Build the frontend (`npm run build`)
+2. Copy static files to `trellis_datamodel/static/`
+3. Build the Python wheel (`uv build`)
+
+The wheel will be in `dist/` and can be installed with `pip install dist/trellis_datamodel-*.whl`.
+
+## CLI Options
+
+```bash
+trellis run [OPTIONS]
+
+Options:
+  --port, -p INTEGER    Port to run the server on [default: 8089]
+  --config, -c TEXT     Path to config file (trellis.yml or config.yml)
+  --no-browser          Don't open browser automatically
+  --help                Show help message
+```
+
+## dbt Metadata
+- Generate `manifest.json` and `catalog.json` by running `dbt docs generate` in your dbt project.
+- The UI reads these artifacts to power the ERD modeller.
+- Without these artifacts, the UI loads but shows no dbt models.
+
+## Configuration
+
+Run `trellis init` to create a starter `trellis.yml` file in your project.
+
+Options:
+
+- `framework`: Transformation framework to use. Currently supported: `dbt-core`. Future: `dbt-fusion`, `sqlmesh`, `bruin`, `pydantic`. Defaults to `dbt-core`.
+- `dbt_project_path`: Path to your dbt project directory (relative to `config.yml` or absolute). **Required**.
+- `dbt_manifest_path`: Path to `manifest.json` (relative to `dbt_project_path` or absolute). Defaults to `target/manifest.json`.
+- `dbt_catalog_path`: Path to `catalog.json` (relative to `dbt_project_path` or absolute). Defaults to `target/catalog.json`.
+- `data_model_file`: Path where the data model YAML will be saved (relative to `dbt_project_path` or absolute). Defaults to `data_model.yml`.
+- `dbt_model_paths`: List of path patterns to filter which dbt models are shown (e.g., `["3_core"]`). If empty, all models are included.
+
+**Example `trellis.yml`:**
+```yaml
+framework: dbt-core
+dbt_project_path: "./dbt_built"
+dbt_manifest_path: "target/manifest.json"
+dbt_catalog_path: "target/catalog.json"
+data_model_file: "data_model.yml"
+dbt_model_paths:
+  - "3_core"
+```
+
+
+## Testing
+
+### Frontend
+**Testing Libraries:**
+The following testing libraries are defined in `package.json` under `devDependencies` and are automatically installed when you run `npm install`:
+- [Vitest](https://vitest.dev/) (Unit testing)
+- [Playwright](https://playwright.dev/) (End-to-End testing)
+- [Testing Library](https://testing-library.com/) (DOM & Svelte testing utilities)
+- [jsdom](https://github.com/jsdom/jsdom) (DOM environment)
+
+> **Playwright system dependencies (Ubuntu/WSL2)**
+>
+> The browsers downloaded by Playwright need a handful of native libraries. Install them before running `npm run test:e2e`:
+>
+> ```bash
+> sudo apt-get update && sudo apt-get install -y \
+>   libxcursor1 libxdamage1 libgtk-3-0 libpangocairo-1.0-0 libpango-1.0-0 \
+>   libatk1.0-0 libcairo-gobject2 libcairo2 libgdk-pixbuf-2.0-0 libasound2 \
+>   libnspr4 libnss3 libgbm1 libgles2-mesa libgtk-4-1 libgraphene-1.0-0 \
+>   libxslt1.1 libwoff2dec0 libvpx7 libevent-2.1-7 libopus0 \
+>   libgstallocators-1.0-0 libgstapp-1.0-0 libgstpbutils-1.0-0 libgstaudio-1.0-0 \
+>   libgsttag-1.0-0 libgstvideo-1.0-0 libgstgl-1.0-0 libgstcodecparsers-1.0-0 \
+>   libgstfft-1.0-0 libflite1 libflite1-plugins libwebpdemux2 libavif13 \
+>   libharfbuzz-icu0 libwebpmux3 libenchant-2-2 libsecret-1-0 libhyphen0 \
+>   libwayland-server0 libmanette-0.2-0 libx264-163
+> ```
+
+**Running Tests:**
+
+The test suite has multiple levels to catch different types of issues:
+
+```bash
+cd frontend
+
+# Quick smoke test (catches 500 errors, runtime crashes, ESM issues)
+# Fastest way to verify the app loads without errors
+npm run test:smoke
+
+# TypeScript/compilation check
+npm run check
+
+# Unit tests
+npm run test:unit
+
+# E2E tests (includes smoke test + full test suite)
+# Note: Requires backend running with test data (see Test Data Isolation below)
+npm run test:e2e
+
+# Run all tests (check + smoke + unit + e2e)
+npm run test
+```
+
+**Test Levels:**
+1. **`npm run check`** - TypeScript compilation errors
+2. **`npm run test:smoke`** - Runtime errors (500s, console errors, ESM issues) - **catches app crashes**
+3. **`npm run test:unit`** - Unit tests with Vitest
+4. **`npm run test:e2e`** - Full E2E tests with Playwright
+
+**Using Makefile:**
+```bash
+# From project root
+make test-smoke     # Quick smoke test
+make test-check     # TypeScript check
+make test-unit      # Unit tests
+make test-e2e       # E2E tests (auto-starts backend with test data)
+make test-all       # All tests
+```
+
+**Test Data Isolation:**
+E2E tests use a separate test data file (`frontend/tests/test_data_model.yml`) to avoid polluting your production data model. **Playwright automatically starts the backend** with the correct environment variable, so you don't need to manage it manually.
+
+```bash
+# Just run E2E tests - backend starts automatically with test data
+make test-e2e
+# OR:
+# cd frontend && npm run test:e2e
+```
+
+The test data file is automatically cleaned before and after test runs via Playwright's `globalSetup` and `globalTeardown`. Your production `data_model.yml` remains untouched.
+
+### Backend
+**Testing Libraries:**
+The following testing libraries are defined in `pyproject.toml` under `[project.optional-dependencies]` in the `dev` group:
+- [pytest](https://docs.pytest.org/) (Testing framework)
+- [httpx](https://www.python-httpx.org/) (Async HTTP client for API testing)
+
+**Installation:**
+Unlike `npm`, `uv sync` does not install optional dependencies by default. To include the testing libraries, run:
+```bash
+cd backend
+uv sync --extra dev
+```
+
+**Running Tests:**
+```bash
+cd backend
+uv run pytest
+```

trellis_datamodel-0.1.2/pyproject.toml

@@ -0,0 +1,71 @@
+[build-system]
+requires = ["setuptools>=61.0", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "trellis-datamodel"
+version = "0.1.2"
+description = "Visual data model editor for dbt projects"
+readme = "README.md"
+requires-python = ">=3.11"
+authors = [
+    {name = "Tim Hiebenthal"},
+]
+keywords = ["dbt", "data-modeling", "erd", "data-engineering", "analytics-engineering", "visualization", "schema"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Database",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+dependencies = [
+    "dbt-core>=1.6,<2.0",
+    "fastapi>=0.121.3",
+    "python-dotenv>=1.2.1",
+    "pyyaml>=6.0.3",
+    "ruamel.yaml>=0.18.0",
+    "typer>=0.9.0",
+    "uvicorn>=0.38.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/timhiebenthal/trellis-datamodel"
+Repository = "https://github.com/timhiebenthal/trellis-datamodel"
+Issues = "https://github.com/timhiebenthal/trellis-datamodel/issues"
+
+[project.scripts]
+trellis = "trellis_datamodel.cli:app"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0.0",
+    "httpx>=0.27.0",
+]
+examples = [
+    "dbt-duckdb==1.10",
+    "duckdb>=1.4.2",
+    "marimo>=0.18.0",
+    "nba-api>=1.11.3",
+    "pandas>=2.3.3",
+    "tqdm>=4.67.1",
+]
+
+[tool.setuptools.packages.find]
+where = ["."]
+include = ["trellis_datamodel*"]
+
+[tool.setuptools.package-data]
+trellis_datamodel = ["static/**/*"]
+
+[tool.pytest.ini_options]
+testpaths = ["trellis_datamodel/tests"]
+pythonpath = ["."]
+
+[dependency-groups]
+dev = [
+    "httpx>=0.28.1",
+    "pytest>=9.0.1",
+]

trellis_datamodel-0.1.2/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

trellis_datamodel-0.1.2/trellis_datamodel/__init__.py

@@ -0,0 +1,3 @@
+"""Trellis Data - Visual data model editor for dbt projects."""
+
+__version__ = "0.1.2"

trellis_datamodel-0.1.2/trellis_datamodel/adapters/__init__.py

@@ -0,0 +1,47 @@
+"""
+Adapter factory for transformation framework integrations.
+
+Provides get_adapter() to instantiate the appropriate adapter based on config.
+"""
+
+from typing import Union
+
+from trellis_datamodel.config import (
+    FRAMEWORK,
+    MANIFEST_PATH,
+    CATALOG_PATH,
+    DBT_PROJECT_PATH,
+    DATA_MODEL_PATH,
+    DBT_MODEL_PATHS,
+)
+from .base import TransformationAdapter
+from .dbt_core import DbtCoreAdapter
+
+
+def get_adapter() -> Union[DbtCoreAdapter, TransformationAdapter]:
+    """
+    Get the appropriate adapter based on the configured framework.
+
+    Returns:
+        An adapter instance implementing TransformationAdapter.
+
+    Raises:
+        ValueError: If the configured framework is not supported.
+    """
+    if FRAMEWORK == "dbt-core":
+        return DbtCoreAdapter(
+            manifest_path=MANIFEST_PATH,
+            catalog_path=CATALOG_PATH,
+            project_path=DBT_PROJECT_PATH,
+            data_model_path=DATA_MODEL_PATH,
+            model_paths=DBT_MODEL_PATHS,
+        )
+
+    raise ValueError(
+        f"Unknown framework: {FRAMEWORK}. "
+        f"Supported frameworks: dbt-core"
+    )
+
+
+__all__ = ["get_adapter", "TransformationAdapter", "DbtCoreAdapter"]
+