Add DEBUG instrumentation and documentation
This commit is contained in:
parent
c5d4021e18
commit
e60222daec
3 changed files with 510 additions and 84 deletions
|
@ -124,5 +124,12 @@ The `fts_tracks_*` tables are managed by SQLite to back the FTS5 virtual table.
|
|||
- Restrict new CSS to scoped utility classes in `site.css`; otherwise rely on Bulma components.
|
||||
- Before submitting changes, verify there are no console warnings, layout adapts from mobile to desktop, and keyboard navigation continues to work.
|
||||
|
||||
### Debug Instrumentation
|
||||
- Enable verbose query diagnostics by setting `localStorage.setItem('mp3com.debug', 'true')` and reloading the app (clear the key or set it to `'false'` to disable).
|
||||
- With DEBUG on, every SQLite statement logs `Query begin` / `Query end` entries that include the originating view, optional label, normalized SQL text, bound parameters, row counts, and execution duration.
|
||||
- Any statement failure logs `[SQLite error]` details (SQL, params, phase, message, stack) before the exception propagates, making it easier to correlate with UI regressions.
|
||||
- Pagination helpers emit `[Pagination]` traces whenever user inputs are normalized or clamped (including high-page corrections after a total count comes back smaller than expected).
|
||||
- Use the `prepareForView(db, VIEW_NAMES.someView, sql, label)` helper when preparing new statements so that console output remains aligned with the feature area generating the query.
|
||||
|
||||
## License
|
||||
Add licensing information here when available.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue