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
{{ message }}
Repository navigation
Feature gap: findings.suggested_fix always NULL for rule-based findings #404
findings.suggested_fix is always NULL for rule-based findings. The body field has a description, but no actionable fix suggestion.
Current State
findings table:
body = "Static security scanner detected: SQL injection via string concatenation in src/engine/db_writer.rs:80"
suggested_fix = NULL
Expected
For deterministic rule-based findings, suggested_fix should contain a brief fix suggestion (e.g., "Use parameterized queries instead of string concatenation").
Proposed Fix
Add fix suggestions to each rule in security_scanner.rs
When saving finding to DB, populate suggested_fix from the rule's suggestion template
Display in cora findings list output
Impact
Users get findings but no guidance on how to fix them
LLM-based reviews do generate suggestions, but rule-based ones do not
Inconsistent UX between LLM and rule-based findings
Activity
chore: v0.9.0 release prep (#423)
chore: sync v0.9.0 release prep to develop (#424)
chore: sync v0.9.0 release prep to develop (#424) (#425)
release: v0.10.0 (#442)
release: v0.11.1 → main (#450)