ripple-sql 0.1.8__tar.gz → 0.1.10__tar.gz

{ripple_sql-0.1.8 → ripple_sql-0.1.10}/CHANGELOG.md

@@ -6,6 +6,16 @@ Notable changes to Ripple. The format follows
 
 ## [Unreleased]
 
+## [0.1.10] - 2026-09-15
+
+### Changed
+- The answer page and `ripple serve` home read as one instrument. Panels sit on a hairline shadow instead of a drawn box. A faint dot grid runs under the graph and under nothing else. Every count beside a name is set in tabular monospace at one size. The wires touching the chosen model carry the accent and the rest recede. Type sits on five sizes (title, prose, the question box, labels, counts); the small text is darker so it reads at 4.5:1; the header counts carry a thousands separator. Motion has two durations, 150 ms for hover and 240 ms for entering, ease-out, on transform and opacity only.
+
+## [0.1.9] - 2026-09-15
+
+### Changed
+- `ripple check-file` no longer needs the table's name in the common case. A file binds to the table its own columns name when they say it clearly: at least two of them are one table's, they are most of the file's columns, and no other table matches as many ("matched by 4 of 5 column names"). `--source` takes the bare table name when one schema has it (`--source vendor_feed`); a name two schemas share is refused with both spellings. When two tables fit a file equally, or none does, the command lists the tables with declared columns and stops with exit 2, never picking one. `--source` and a declared `files:` pattern still come first. A review of the command's edge cases also fixed: a column read only in a where clause or a join now counts as read; a reader the graph only sees through select star counts instead of vanishing; long chains are counted whole; an xlsx is read by the workbook's own sheet order, streamed no further than its first row, with rich text joined and empty cells kept as positions; tab-separated `.txt` and semicolon `.csv` files are read by their delimiter; a file that is not UTF-8 asks for `--encoding`; an unclosed quote, a duplicated header name, a DOCTYPE in the XML, a broken xlsx part, a pyarrow older than 14.0.1 and a broken `ripple.yml` are each a plain message with exit 2; a folder pattern (`incoming/*.csv`) matches the file's path; two patterns that name two tables are refused; `--source` never reads the pattern map; a missing file, a folder, and a project that cannot load give the same JSON shape as any other failure.
+
 ## [0.1.8] - 2026-09-15
 
 ### Added
@@ -270,7 +280,9 @@ First public release.
 ### Removed
 - The dark whole-graph canvas that `ripple serve` used to open (`static/index.html`). Every surface now draws one answer.
 
-[Unreleased]: https://github.com/bteh/ripple/compare/v0.1.8...HEAD
+[Unreleased]: https://github.com/bteh/ripple/compare/v0.1.10...HEAD
+[0.1.10]: https://github.com/bteh/ripple/releases/tag/v0.1.10
+[0.1.9]: https://github.com/bteh/ripple/releases/tag/v0.1.9
 [0.1.8]: https://github.com/bteh/ripple/releases/tag/v0.1.8
 [0.1.7]: https://github.com/bteh/ripple/releases/tag/v0.1.7
 [0.1.6]: https://github.com/bteh/ripple/releases/tag/v0.1.6

{ripple_sql-0.1.8 → ripple_sql-0.1.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ripple-sql
-Version: 0.1.8
+Version: 0.1.10
 Summary: Offline column-level SQL lineage. See what breaks before you merge.
 Project-URL: Homepage, https://github.com/bteh/ripple
 Project-URL: Repository, https://github.com/bteh/ripple
@@ -240,7 +240,7 @@ Stop: 2 columns that 4 models read are missing from this file. (exit 1)
 
 The first line and the last are the same sentence, so the vendor's screenshot and the engineer's scrolled terminal both end on the verdict. Exit 0 means nothing downstream changes (a new column nobody reads is fine), 1 means something breaks, 2 means the check could not run. Header only: no data row is read and nothing leaves the machine.
 
-The file finds its table through `--source raw.vendor_feed`, or through a pattern the project declares once:
+The file finds its table by its own columns when they say it clearly (most of them belong to one table and no other table comes close: "matched by 4 of 5 column names"), by `--source vendor_feed` (the bare table name is enough when one schema has it), or by a pattern the project declares once:
 
 ```yaml
 sources:
@@ -255,7 +255,7 @@ sources:
           - name: customer_name
 ```
 
-A plain SQL folder keeps the same map in `ripple.yml` (`files: {"vendor_feed_*.csv": raw.vendor_feed}`). The table's declared columns are the contract: `columns:` in sources.yml, a seed, or a list from `ripple ingest-schema`. Reads csv, tsv, xlsx and parquet (parquet needs pyarrow installed). `--json` carries the same facts for an ingest job.
+A plain SQL folder keeps the same map in `ripple.yml` (`files: {"vendor_feed_*.csv": raw.vendor_feed}`). When two tables fit the file equally, or none does, the command lists the tables it can check and stops with exit 2 rather than pick one. The table's declared columns are the contract: `columns:` in sources.yml, a seed, or a list from `ripple ingest-schema`. Reads csv, tsv, xlsx and parquet (parquet needs pyarrow 14.0.1 or newer). A file that is not UTF-8 takes `--encoding cp1252`. `--json` carries the same facts for an ingest job, in the same shape whether the check ran or could not.
 
 ## Bring your query history (optional)
 

{ripple_sql-0.1.8 → ripple_sql-0.1.10}/README.md

@@ -200,7 +200,7 @@ Stop: 2 columns that 4 models read are missing from this file. (exit 1)
 
 The first line and the last are the same sentence, so the vendor's screenshot and the engineer's scrolled terminal both end on the verdict. Exit 0 means nothing downstream changes (a new column nobody reads is fine), 1 means something breaks, 2 means the check could not run. Header only: no data row is read and nothing leaves the machine.
 
-The file finds its table through `--source raw.vendor_feed`, or through a pattern the project declares once:
+The file finds its table by its own columns when they say it clearly (most of them belong to one table and no other table comes close: "matched by 4 of 5 column names"), by `--source vendor_feed` (the bare table name is enough when one schema has it), or by a pattern the project declares once:
 
 ```yaml
 sources:
@@ -215,7 +215,7 @@ sources:
           - name: customer_name
 ```
 
-A plain SQL folder keeps the same map in `ripple.yml` (`files: {"vendor_feed_*.csv": raw.vendor_feed}`). The table's declared columns are the contract: `columns:` in sources.yml, a seed, or a list from `ripple ingest-schema`. Reads csv, tsv, xlsx and parquet (parquet needs pyarrow installed). `--json` carries the same facts for an ingest job.
+A plain SQL folder keeps the same map in `ripple.yml` (`files: {"vendor_feed_*.csv": raw.vendor_feed}`). When two tables fit the file equally, or none does, the command lists the tables it can check and stops with exit 2 rather than pick one. The table's declared columns are the contract: `columns:` in sources.yml, a seed, or a list from `ripple ingest-schema`. Reads csv, tsv, xlsx and parquet (parquet needs pyarrow 14.0.1 or newer). A file that is not UTF-8 takes `--encoding cp1252`. `--json` carries the same facts for an ingest job, in the same shape whether the check ran or could not.
 
 ## Bring your query history (optional)
 

{ripple_sql-0.1.8 → ripple_sql-0.1.10}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ripple-sql"
-version = "0.1.8"
+version = "0.1.10"
 description = "Offline column-level SQL lineage. See what breaks before you merge."
 readme = "README.md"
 requires-python = ">=3.10"