Subcategory: Error handling & CLI UX
Score: 8 → 10 (target)
src/pycharting/api/interface.py:248 wraps the entire plot body in a single broad except Exception, collapsing distinct failure modes (input validation vs. server startup vs. browser launch) into one generic {"status": "error", "error": str(e)}.
Suggested fix: catch DataValidationError separately from server-startup/runtime errors so the returned error (and the printed message) tells the user which stage failed and how to fix it.
Done when: plot distinguishes validation failures from server/runtime failures in its returned result.
Subcategory: Error handling & CLI UX
Score: 8 → 10 (target)
src/pycharting/api/interface.py:248wraps the entireplotbody in a single broadexcept Exception, collapsing distinct failure modes (input validation vs. server startup vs. browser launch) into one generic{"status": "error", "error": str(e)}.Suggested fix: catch
DataValidationErrorseparately from server-startup/runtime errors so the returnederror(and the printed message) tells the user which stage failed and how to fix it.Done when:
plotdistinguishes validation failures from server/runtime failures in its returned result.