Skip to content

Keep a conversation view's data values as the artifact wrote them - #2233

Merged
abrignoni merged 1 commit into
mainfrom
fix/lava-conversation-view-values
Sep 19, 2026
Merged

abrignoni merged 1 commit into
mainfrom
fix/lava-conversation-view-values

Conversation

@abrignoni

Copy link
Copy Markdown
Owner

Fixes conversation views in LAVA.

  • directionSentValue and sentMessageStaticLabel carry data, not column names, so they now reach the manifest as the artifact wrote them. Column keys are sanitized as before.
  • A direction value of 'Sent' beside a 'Sent' time column used to be stored as 'sent', so nothing matched it and every message showed as received.
  • No shipped artifact's manifest changes: none of the 103 conversation views across the five tools has a sent value or a static label that matches one of its headers.

Adds admin/test/scripts/test_lava_conversation_view_values.py, which fails on three of its five cases against the old writer.

🤖 Generated with Claude Code

lava_process_artifact turned every data_views value that matched a column
header into that column's SQL name. Two of those keys carry data rather than a
column name: LAVA reads directionSentValue and sentMessageStaticLabel as
written and resolves every other key to a column. So a direction value of
'Sent' beside a 'Sent' time column reached the manifest as 'sent', no row
matched it, and LAVA's conversation view showed every message as received.

Those two keys now pass through unchanged, and column keys are sanitized as
before. No shipped artifact's manifest changes: none of the 103 conversation
views across the five tools uses a sent value or a static label that matches
one of its own headers.

The new test fails on three of its five cases against the old writer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@abrignoni
abrignoni merged commit d42b55d into main Sep 19, 2026
8 checks passed
@abrignoni
abrignoni deleted the fix/lava-conversation-view-values branch September 19, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant