#137 — Make ECharts/Table headers user-friendly and avoid empty labels

Repo: Twill-AI/twill-llm-engine State: closed | Status: done Assignee: meliascosta

Created: 2024-09-24 · Updated: 2024-11-19

Description

Caused by https://twill-network.slack.com/archives/C06UCQP1BFC/p1727087760427069

If open https://ca-staging-twill-facade-eastus.happystone-888ee9bf.eastus.azurecontainerapps.io/api/v1/llmchats/56/items?limit=10&include_sources=false&include_widgets=true for user@twillpayments.com (in https://ca-staging-twill-facade-eastus.happystone-888ee9bf.eastus.azurecontainerapps.io/docs#/llmchats/get_llmchat_items_api_v1_llmchats__llmchat_id__items_get) and find 506 item with "type": "ChatResponseEcharts" then it would show:

\"headers\":[\"item_description\",\"item_price\",\"issue_date\"]

While better to have something like [Description, Price, Issue Date].

Next it contains items without description (because description is optional field in Rutter):

\"headers\":[ ... [null,564,\"2024-08-16 00:00:00\"] ... ]

If look on relevant bill entities for such bill_line_item-s then they would have “memo=Bill synced from Melio.” (looks like https://meliopayments.com/). But for user any description="" causes frustration - hard to understand what it is. And getting a lot of bars on plot without label perceived by the user as an app error.

AC:

  • Provide headers into Echarts and Table responses in user-friendly format, not like they are named in SQL.
  • Try to avoid “no value” cells in Echarts and Table responses. Either find all available information or show nothing. In the example above it may be show in 2 options:
    1. With text `(no description provided, rel

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets