Lars/mitai-jinkendo
1
0
Fork 0
Code Issues 23 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

docs: Quality-Level Parameter für KI-Analysen notiert (#28)
All checks were successful
Deploy Development / deploy (push) Successful in 45s
Details
Build Test / lint-backend (push) Successful in 0s
Details
Build Test / build-frontend (push) Successful in 13s
Details

Browse Source 
Notiert an 3 Stellen:
1. insights.py: TODO-Kommentar im Code
2. ROADMAP.md: Deliverable bei M0.2 (lokal, nicht im Git)
3. Gitea Issue #28: Kommentar mit Spezifikation

Zukünftig:
- GET /api/insights/run/{slug}?quality_level=quality
- 4 Stufen: all, quality, very_good, excellent
- Frontend: Dropdown wie in History.jsx
- Pipeline-Configs können Standard-Level haben

User-Request: Quality-Level-Auswahl für KI-Analysen

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Lars 2026-03-23 22:06:30 +01:00
parent 848ba0a815
commit b317246bcd
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
backend/routers/insights.py
View File

@ -76,6 +76,8 @@ def _get_profile_data(pid: str):
cur.execute("SELECT * FROM nutrition_log WHERE profile_id=%s ORDER BY date DESC LIMIT 90", (pid,)) cur.execute("SELECT * FROM nutrition_log WHERE profile_id=%s ORDER BY date DESC LIMIT 90", (pid,))
nutrition = [r2d(r) for r in cur.fetchall()] nutrition = [r2d(r) for r in cur.fetchall()]
# Quality-Filter: nur hochwertige Aktivitäten für KI-Analyse (Issue #24) # Quality-Filter: nur hochwertige Aktivitäten für KI-Analyse (Issue #24)
# TODO (#28): quality_level als Parameter (all, quality, very_good, excellent)
# Zukünftig: GET /api/insights/run/{slug}?quality_level=quality
cur.execute(""" cur.execute("""
SELECT * FROM activity_log SELECT * FROM activity_log
WHERE profile_id=%s WHERE profile_id=%s