fix: update helpdesk doubt parsing for new query_type schema - #232
Conversation
|
Claude finished @pugal66's task in 2m 4s —— View job Reviewed PR #232 — fix: update helpdesk doubt parsing for new query_type schema
PR Review Summary✅ What's good
🔴 CRITICAL — Must fix before mergeNone found. 🟡 WARNING — Should fix
🔵 SUGGESTION — Nice to have
VerdictCHANGES REQUESTED — the DTO fix itself is correct and safe to ship, but the list-filter query-type gap (#1 above) is closely related to this exact schema migration and should at least be verified before merge to avoid a follow-up bug report; the missing test (#2) is a lower-severity nice-to-have. |
7df2cd3 to
ff015cd
Compare
|
@claude review |
|
Claude finished @pugal66's task in 1m 31s —— View job Reviewed PR #232 — fix: update helpdesk doubt parsing for new query_type schema
PR Review SummaryThis is a re-review after the latest commit ( ✅ What's good
🔴 CRITICAL — Must fix before mergeNone found. 🟡 WARNING — Should fixNone found — both prior warnings (filter path, missing test) have been addressed. 🔵 SUGGESTION — Nice to have
VerdictAPPROVED — the DTO fix, the query-type filter fix, and the added regression test all look correct and consistent with existing conventions. Remaining items are minor polish only. |
ff015cd to
0357b8d
Compare
0357b8d to
4ab91e8
Compare
What changed?
DoubtDtoto read thequery_type_displaystring from the API response instead ofquery_type.Why?
query_typeand a string forquery_type_display. This ensures our parsing logic uses the new string field so that 'AI' and 'Mentor' doubts are identified correctly without breaking.