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
Add Dapper.Sqlite sample (async + tx), introduce ADO QueryWatchTransaction for parity, update docs on redactor ordering & Dapper budgets, and add central Dapper package version
Copy file name to clipboardExpand all lines: README.md
+27Lines changed: 27 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,3 +72,30 @@ When run inside GitHub Actions, the CLI writes a Markdown table to the **Step Su
72
72
### Note on per‑pattern budgets
73
73
74
74
Budgets match against the `events` captured in the JSON file(s). These are the top‑N slowest events by duration to keep files small. If you want strict coverage, export with a higher `sampleTop` in `QueryWatchJson.ExportToFile`, or pass a larger `sampleTop` to `QueryWatchScope.Start(...)`.
75
+
76
+
## Redactor ordering tips
77
+
78
+
If you use multiple redactors, **order matters**. A safe, effective default is:
79
+
80
+
1.**Whitespace normalizer** – make SQL text stable across environments/providers.
81
+
2.**High‑entropy token masks** – long hex tokens, JWTs, API keys.
82
+
3.**PII masks** – emails, phone numbers, IPs.
83
+
4.**Custom rules** – your app–specific patterns (use `AddRegexRedactor(...)`).
84
+
85
+
> Put *broad* rules (like whitespace) first, and *specific* rules (like PII) after. This lowers the chance one rule prevents another from matching.
86
+
87
+
## Typical budgets for Dapper‑heavy solutions
88
+
89
+
Dapper often issues *fewer, more targeted* commands than ORMs. Reasonable starting points (tune per project):
90
+
91
+
-**End‑to‑end web test:**`--max-queries 40`, `--max-average-ms 50`, `--max-total-ms 1500`.
0 commit comments