Skip to content

Commit b303c82

Browse files
committed
Fix canonical dxt expansion
1 parent 0011f5d commit b303c82

5 files changed

Lines changed: 11 additions & 4 deletions

File tree

AGENTS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Agent Instructions
22

3-
This repository is building `dxt`, the Data Transformation eXecutor: a dbt-project-compatible transformation engine with an artifact-first compatibility strategy and later cross-database execution.
3+
This repository is building `dxt`, Data eXecution & Transformation: a dbt-project-compatible transformation engine with an artifact-first compatibility strategy and later cross-database execution.
44

55
Hard requirement: the `dxt` product runtime is Zig. Python may remain only for developer scripts, tests, fixture tooling, compatibility harnesses, and safety scans. Do not implement product CLI, parser, compiler, artifact writer, planner, adapter, or runtime behavior in Python.
66

PLAN.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Name And Product Contract
44

5-
`dxt` means **Data Transformation eXecutor**.
5+
`dxt` means **Data eXecution & Transformation**.
66

77
The product goal is a dbt-project-compatible transformation engine written in Zig. The first promise is compatibility with dbt Core project semantics and artifacts, not a private or unofficial dbt fork. Fusion-era capabilities, semantic resources, metrics, static analysis, and cross-database planning shape the architecture, but dbt Core compatibility is the required base.
88

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# dxt
22

3-
`dxt` is the **Data Transformation eXecutor**: a dbt-project-compatible transformation engine written in Zig.
3+
`dxt` is **Data eXecution & Transformation**: a dbt-project-compatible transformation engine written in Zig.
44

55
The first target is dbt Core compatibility for public projects such as Jaffle Shop. The long-term architecture also accounts for semantic resources, metrics, Fusion-style static analysis, and efficient cross-database execution.
66

src/root.zig

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -251,7 +251,7 @@ pub fn printRootHelp(writer: *Io.Writer) !void {
251251
try writer.writeAll(
252252
\\Usage: dxt [--version] <command> [options]
253253
\\
254-
\\Data Transformation eXecutor: a dbt-project-compatible transformation engine.
254+
\\Data eXecution & Transformation: a dbt-project-compatible transformation engine.
255255
\\
256256
\\Commands:
257257
\\ version Print the dxt version.

tests/test_cli.py

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,13 @@ def test_version_command():
5050
assert result.stderr == ""
5151

5252

53+
def test_root_help_uses_canonical_name():
54+
result = subprocess.run([DXT, "--help"], cwd=ROOT, check=True, text=True, capture_output=True)
55+
assert "Data eXecution & Transformation" in result.stdout
56+
assert "Data Transformation eXecutor" not in result.stdout
57+
assert result.stderr == ""
58+
59+
5360
def copy_fixture(tmp_path: Path, name: str) -> Path:
5461
source = ROOT / "tests" / "fixtures" / name
5562
dest = tmp_path / name

0 commit comments

Comments
 (0)