You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/demo.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Try `Recce` without installing using this [online demo](https://pr1.cloud.datare
12
12
The demo showcases a [pull request](https://github.com/DataRecce/jaffle_shop_duckdb/pull/1) that fixes the `customer_lifetime_value` calculation in dbt's Jaffle Shop project to only included completed orders.
@@ -26,7 +26,7 @@ Some example validation checks you might create include:
26
26
Run a [Value Diff](features/lineage.md#value-diff) to check the percentage match of the `customer_lifetime_value` column between production and the development branch.
27
27
28
28
<figuremarkdown>
29
-

29
+

In models classified as **non-breaking** or **partial breaking** - added, removed, or modified columns will be listed. Click on a column to open its [Column-Level Lineage](./column-level-lineage.md)
@@ -264,7 +264,7 @@ To select a node and all of its parents or children:
264
264
3. Click to select either parent or child nodes.
265
265
266
266
<figuremarkdown>
267
-
{: .shadow}
267
+
{: .shadow}
268
268
<figcaption>Select a node and its parents or children</figcaption>
269
269
</figure>
270
270
@@ -273,7 +273,7 @@ To select a node and all of its parents or children:
273
273
After selecting the desired nodes, use the Actions menu at the top right of the screen to perform diffs or add checks.
274
274
275
275
<figuremarkdown>
276
-
{: .shadow}
276
+
{: .shadow}
277
277
<figcaption>Perform actions on multiple nodes</figcaption>
278
278
</figure>
279
279
@@ -282,7 +282,7 @@ After selecting the desired nodes, use the Actions menu at the top right of the
282
282
An example of selecting multiple nodes to perform a multi-node row count diff:
283
283
284
284
<figuremarkdown>
285
-
{: .shadow}
285
+
{: .shadow}
286
286
<figcaption>Perform a Row Count Diff on multiple nodes</figcaption>
287
287
</figure>
288
288
@@ -291,7 +291,7 @@ An example of selecting multiple nodes to perform a multi-node row count diff:
291
291
An example of selecting multiple nodes to perform a multi-node Value Diff:
292
292
293
293
<figuremarkdown>
294
-
{: .shadow}
294
+
{: .shadow}
295
295
<figcaption>Perform a Value Diff on multiple nodes</figcaption>
296
296
</figure>
297
297
@@ -302,7 +302,7 @@ An example of selecting multiple nodes to perform a multi-node Value Diff:
302
302
In the diff result, we can find a **Copy to Clipboard** button. it's a handy feature to copy the result image to clipboard and paste in your PR comment.
303
303
304
304
<figuremarkdown>
305
-
{: .shadow}
305
+
{: .shadow}
306
306
<figcaption>Copy a diff result screenshot to the clipboard and paste to GitHub</figcaption>
307
307
</figure>
308
308
@@ -326,7 +326,7 @@ From the Lineage DAG, click the Actions dropdown menu and click Lineage Diff or
326
326
- Schema Diff: A diff of all nodes if none are selected, or specific <ahref="#multi-node-selection">selected nodes</a>.
327
327
328
328
<figuremarkdown>
329
-
{: .shadow}
329
+
{: .shadow}
330
330
<figcaption>Add a Lineage Diff Check or Schema Check via the Actions dropdown menu</figcaption>
331
331
</figure>
332
332
@@ -335,14 +335,14 @@ From the Lineage DAG, click the Actions dropdown menu and click Lineage Diff or
335
335
For the majority of diffs, which are performed via the Explore Change dropdown menu, the Check can be added by clicking the Add to Checklist button in the results panel:
336
336
337
337
<figuremarkdown>
338
-
{: .shadow}
338
+
{: .shadow}
339
339
<figcaption>Add a Check by clicking the Add to Checklist button in the diff results panel</figcaption>
340
340
</figure>
341
341
342
342
343
343
An example performing a Top-K diff and adding the results to the Checklist:
344
344
345
345
<figuremarkdown>
346
-
{: .shadow}
346
+
{: .shadow}
347
347
<figcaption>Example adding a Top-K Diff to the Checklist</figcaption>
Copy file name to clipboardExpand all lines: docs/features/query.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,15 +24,15 @@ select * from {{ ref("mymodel") }}
24
24
25
25
If the primary key(s) is specified, the query will occur in the warehouse; otherwise, the query will happen across two environments and the comparison will take place on the client side.
-**Primary Key:** When comparison occurs on the client side, we can select the primary key by clicking the `key` icon. The primary key columns are used to be identified as the same record for both sides. If no primary key is specified, the records is compared by the row's index.
38
38
-**Pinned Column:** The pinned column would show first in the column list.
Copy file name to clipboardExpand all lines: docs/features/state-file.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ There are multiple ways to save the state file.
19
19
1.**Save from the Web UI**: Click the **Save** button at the top of the app. Recce will continuously write updates to the state file, effectively working like an auto-save feature, and persist the state until the Recce instance is closed. The file is saved with the specified filename in the directory where the recce server command is run.
20
20
21
21
1.**Export from the Web UI**: Click the **Export** button located in the top-right corner to download the current Recce state to any location on your machine.
1.**Start Recce from a State File**: You can provide a state file as an argument when launching Recce. If the file does not exist, Recce will create a state file and start with an empty state. If the file exists, Recce will load the state and continue working from it.
25
25
```
@@ -68,7 +68,7 @@ Common development workflow:
68
68
recce server recce_issue_1.json
69
69
```
70
70
71
-

71
+

72
72
73
73
## Scenario: PR Review
74
74
@@ -87,7 +87,7 @@ During the PR review process, the state file serves as a communication medium be
87
87
recce server --review recce_issue_1.json
88
88
```
89
89
90
-

90
+

0 commit comments