forked from jsnbuchanan/crowd-funder-for-time-pwa
a41ce0cd4c
- Fix logToDb() to use actual database schema: 'date' and 'message' columns - Change INSERT query from non-existent 'timestamp, level' to existing 'date, message' - Change DELETE cleanup to use 'date' column instead of 'timestamp' - Embed log level in message text as '[LEVEL] message' instead of separate column - Use toDateString() format to match schema instead of toISOString() Resolves: "table logs has no column named timestamp" infinite error loop Critical: Enables Electron app initialization by matching code to existing schema Impact: Stops database logging from crashing and allows normal app startup
32 lines
1.2 KiB
Plaintext
32 lines
1.2 KiB
Plaintext
---
|
|
description:
|
|
globs:
|
|
alwaysApply: true
|
|
---
|
|
use system date command to timestamp all interactions with accurate date and time
|
|
python script files must always have a blank line
|
|
remove whitespace at the end of lines
|
|
never git add or commit for me. always preview changes and commit message to use and allow me to copy and paste
|
|
✅ Preferred Commit Message Format
|
|
|
|
Short summary in the first line (concise and high-level).
|
|
Avoid long commit bodies unless truly necessary.
|
|
|
|
✅ Valued Content in Commit Messages
|
|
|
|
Specific fixes or features.
|
|
Symptoms or problems that were fixed.
|
|
Notes about tests passing or TS/linting errors being resolved (briefly).
|
|
|
|
❌ Avoid in Commit Messages
|
|
|
|
Vague terms: “improved”, “enhanced”, “better” — especially from AI.
|
|
Minor changes: small doc tweaks, one-liners, cleanup, or lint fixes.
|
|
Redundant blurbs: repeated across files or too generic.
|
|
Multiple overlapping purposes in a single commit — prefer narrow, focused commits.
|
|
Long explanations of what can be deduced from good in-line code comments.
|
|
|
|
Guiding Principle
|
|
|
|
Let code and inline documentation speak for themselves. Use commits to highlight what isn't obvious from reading the code.
|