Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(chat): Remove loading dots from context display #7557

Merged
merged 2 commits into from
Mar 27, 2025

Conversation

abeatrix
Copy link
Contributor

Follows up on #7502 which add the LoadingDots at Transcript level, where the LoadingDots will show up at the end of the transcript when there is an assistant message in progress.

This commit refactors the ContextCell component to remove the LoadingDots component and simplify the display of context items.

The LoadingDots component was previously used to indicate that the context was loading. However, it was only displayed when isContextLoading was true and isAgenticChat was false. This logic was removed, and the context items are now always displayed within the AccordionContent.

This change simplifies the component and improves the user experience by providing a consistent display of context items, regardless of the loading state or chat mode.

Test Plan

Ensures there are no multple loading dots showing up in the UI at any time.

Follows up on #7502 which add the LoadingDots at Transcript level, where the LoadingDots will show up at the end of the transcript when there is an assistant message in progress.

This commit refactors the `ContextCell` component to remove the `LoadingDots` component and simplify the display of context items.

The `LoadingDots` component was previously used to indicate that the context was loading. However, it was only displayed when `isContextLoading` was true and `isAgenticChat` was false. This logic was removed, and the context items are now always displayed within the `AccordionContent`.

This change simplifies the component and improves the user experience by providing a consistent display of context items, regardless of the loading state or chat mode.

## Test Plan

Ensures there are no multple loading dots showing up in the UI at any time.
Copy link
Contributor

@dominiccooney dominiccooney left a comment

Choose a reason for hiding this comment

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

Thank you for fixing this!

Could you add a touch more detail to the test plan? Verifying that they don't appear "at any time" covers a lot... If any load triggers it, the test plan can just be that: Step 1, make a chat and verify that there's only one set of dots. Done.

@abeatrix abeatrix enabled auto-merge (squash) March 26, 2025 19:40
@abeatrix abeatrix merged commit 656e2c3 into main Mar 27, 2025
20 of 22 checks passed
@abeatrix abeatrix deleted the bee/loading-dots branch March 27, 2025 21:47
abeatrix added a commit that referenced this pull request Mar 28, 2025
…ay (#7597)

Follows up on #7502 which add
the LoadingDots at Transcript level, where the LoadingDots will show up
at the end of the transcript when there is an assistant message in
progress.

This commit refactors the `ContextCell` component to remove the
`LoadingDots` component and simplify the display of context items.

The `LoadingDots` component was previously used to indicate that the
context was loading. However, it was only displayed when
`isContextLoading` was true and `isAgenticChat` was false. This logic
was removed, and the context items are now always displayed within the
`AccordionContent`.

This change simplifies the component and improves the user experience by
providing a consistent display of context items, regardless of the
loading state or chat mode.

## Test Plan

Ensures there are no multple loading dots showing up in the UI at any
time.
 <br> Backport 656e2c3 from #7557

Co-authored-by: Beatrix <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants