Live PB schema probe (2026-08-11) confirmed `driver` and `item_status="driver_pool"` are not in the schema; referencing either in a filter hard-400s the whole query. The driver app's getMyAssignedItems already used the canonical `drv_id` + `item_status="assigned"` pair, so a defensive OR-fallback against the missing fields would have BROKEN the query (not rescued it); that attempt was reverted. Items 'assigned' by the operator (WFDash) app never reach the driver's Assigned tab because the operator-side filter still references those non-existent identifiers. Operator app needs to filter/write `drv_id` and `item_status="assigned"` instead. Also restored the dropped OrderItem.expand definition (each component was accessing item.expand.* unchecked) and widened the item_status union to include 'invoiced' and 'problem' seen in the live schema. Co-authored-by: Orca <help@stably.ai> |
||
|---|---|---|
| .. | ||
| hooks.ts | ||
| itemsCache.ts | ||
| pocketbase.ts | ||
| pwa.ts | ||
| theme.ts | ||
| types.ts | ||
| utils.ts | ||