-
Notifications
You must be signed in to change notification settings - Fork 20
fix: improve layout and scrolling in settings panels #90
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
Conversation
- Fix flex layout and padding in ConversationSettings - Remove problematic overflow-auto from RightSidebarContent - Simplify tools configuration description - Clean up conversation loading logic in useConversation hook
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to dce0fae in 47 seconds. Click for details.
- Reviewed
70lines of code in4files - Skipped
0files when reviewing. - Skipped posting
6draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. src/components/ConversationSettings.tsx:50
- Draft comment:
Addingh-fullto the container ensures the panel fills its parent’s height. Verify that the parent element has an explicit height set. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
2. src/components/ConversationSettings.tsx:88
- Draft comment:
Bottom padding reduced from 'pb-24' to 'pb-12'. Confirm this spacing adjustment matches the design specs. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
3. src/components/ConversationSettings.tsx:229
- Draft comment:
Replaced sticky footer classes with 'flex-shrink-0'. Ensure that the submit button scrolling behavior is as intended since it will no longer remain fixed. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
4. src/components/RightSidebarContent.tsx:36
- Draft comment:
Removed the 'overflow-auto' class from the container. Check that inner components handle scrolling to prevent content overflow issues. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
5. src/components/settings/ToolsConfiguration.tsx:54
- Draft comment:
Simplified the tools configuration description text. This improves clarity; ensure the shortened text still meets user needs. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
6. src/hooks/useConversation.ts:68
- Draft comment:
Refactored the check for existing messages usingconversation$?.data.log.get()?.length. Confirm thatlog.get()reliably returns an array and that this change aligns with reactive state management. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
Workflow ID: wflow_tjfgBxZP7MPaxbh9
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
…l prompts Previously, the SSE connection would create a new session instead of reusing the session from createConversation(), causing interrupts to fail with 404 because generation was on a different session than the interrupt request. Changes: - Pass existing session_id to SSE endpoint to reuse the same session - Prevent createConversation() from overwriting SSE-established sessions - Add onConnected callback to track when SSE connection is established Fixes interrupt functionality on initial conversation prompts and resolves related 404 errors for tool confirmations. Related: #92
- Implement onConnected callback to properly track SSE connection state - Fix setConnected being called immediately instead of on SSE connect - Change .get() to .peek() for performance (avoid unnecessary reactivity) - Add debug logging to help troubleshoot streaming and connection issues - Improve placeholder message handling logic Related to the interrupt fix - ensures connection state is properly synchronized with SSE events. Related: #92
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caution
Changes requested ❌
Reviewed dd8ec0f in 1 minute and 51 seconds. Click for details.
- Reviewed
98lines of code in1files - Skipped
0files when reviewing. - Skipped posting
2draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. src/hooks/useConversation.ts:68
- Draft comment:
Using .peek() instead of .get() bypasses reactivity. Confirm that this change is intentional, as it may affect state updates. - Reason this comment was not posted:
Comment looked like it was already resolved.
2. src/hooks/useConversation.ts:303
- Draft comment:
Moving setConnected(...) inside the onConnected callback is cleaner. Ensure that the API reliably triggers onConnected, as this change removes the immediate connection update. - Reason this comment was not posted:
Comment looked like it was already resolved.
Workflow ID: wflow_oxprPyVYbKtUruoW
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
| existingConversation && existingConversation.data.log.length > 0; | ||
|
|
||
| const hasExistingMessages = conversation$?.data.log.peek()?.length > 0; | ||
| console.log('[useConversation] Loading conversation', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The newly added console.log statements (e.g., logging conversation load info) may be too verbose for production. Consider gating these behind a debug flag or using a proper logging utility.
Add guards to only update selectedConversation$ and selectedTask$ when the value actually changes, preventing unnecessary re-renders and potential infinite loops.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed d2f4198 in 41 seconds. Click for details.
- Reviewed
29lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. src/components/MainLayout.tsx:89
- Draft comment:
Good update – checking if the current state already matches the new value avoids unnecessary updates and re-renders. The conditional clearing (only resetting if not already empty) adds extra safety. Consider adding a brief comment that conversationId takes precedence over taskId when both are provided. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
Workflow ID: wflow_Nvg7WROsGUVMGiPb
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
Removed verbose console.log statements that were printing on every token received during streaming. Kept only the important warning for when there's no assistant message to append to.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed bc6e093 in 34 seconds. Click for details.
- Reviewed
26lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. src/hooks/useConversation.ts:160
- Draft comment:
Removed excessive console logs in the onToken callback for cleaner output. If you need debug logging in development, consider gating logs behind a debug flag or using a logging library. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
Workflow ID: wflow_eeicHALXG3irrXkk
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
Important
Improve layout and scrolling in settings panels, refine conversation loading logic, and enhance session handling.
flexlayout andpaddinginConversationSettings.overflow-autofromRightSidebarContent.ToolsConfiguration.useConversationto handle existing messages and connection states more efficiently.ApiClient.MainLayoutto handle conversation and task selection more robustly.This description was created by
for bc6e093. You can customize this summary. It will automatically update as commits are pushed.