Skip to content

Conversation

@ArthurKnaus
Copy link
Member

Screen.Recording.2025-11-06.at.17.33.05.mov

@ArthurKnaus ArthurKnaus requested a review from a team November 7, 2025 07:19
@ArthurKnaus ArthurKnaus requested a review from a team as a code owner November 7, 2025 07:19
@linear
Copy link

linear bot commented Nov 7, 2025

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 7, 2025
{key: SpanFields.TIMESTAMP, name: t('Timestamp')},
] as const;
const columnWidths: Partial<Record<GenerationFields, number>> = {
[SpanFields.SPAN_ID]: 100,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Mismatched Span ID Enum Breaks Column Widths

The columnWidths map uses SpanFields.SPAN_ID but the table rendering and default fields use SpanFields.ID. These are different enum values ('span_id' vs 'id'), causing the column width configuration to never match and apply to the actual ID column being rendered.

Fix in Cursor Fix in Web


return (
<div>
<Container>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: ForceCellGrow Fails After Field Key Change

The forceCellGrow check uses SpanFields.GEN_AI_REQUEST_MESSAGES, but after the changes this field is no longer a valid column key since it's been replaced by INPUT_OUTPUT_FIELD in the column configuration. This will cause the force cell grow logic to never trigger.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants