-
Notifications
You must be signed in to change notification settings - Fork 1
release-3.1.0 #6
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
…mprove button visibility
…ng state, and improve scroll button styles
…ncies; upgrade vite version
…nd clarify samesite policy
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.
Pull Request Overview
This PR prepares the codebase for the upcoming release 3.1.0 by updating security settings, refining UI styling, and enhancing chat component behavior. Key changes include:
- Updating cookie security settings in the API routes.
- Adjustments to CSS for improved styling of chat components.
- Enhancements to chat components (ChatMessageUser, ChatMessageBot, ChatInput) including new loading state and input validations.
Reviewed Changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/api/routes.py | Updated cookie attributes for secure and samesite values. |
| client/src/main.css | Modified CSS for scrollbar colors, chat container positioning and class name updates. |
| client/src/components/chat/ChatMessageUser.jsx | Added new component to display user messages. |
| client/src/components/chat/ChatMessageBot.jsx | Renamed and reorganized bot message component imports. |
| client/src/components/chat/ChatLayout.jsx | Updated to use new chat message components and integrated loading state. |
| client/src/components/chat/ChatInput.jsx | Enhanced input behavior with maxLength enforcement, error handling, and icon update. |
| client/src/components/LogoutPop.jsx | Minor styling adjustments for logout dialog. |
Files not reviewed (1)
- client/package-lock.json: Language not supported
Comments suppressed due to low confidence (1)
client/src/components/chat/ChatInput.jsx:38
- [nitpick] Verify whether reducing maxRows from 8 to 7 is intentional as it may affect the visibility of the input area for multi-line messages.
maxRows={7}
| secure=False, # TODO: Set to True in production with HTTPS | ||
| samesite='Lax', # TODO: Set to 'Lax' in production with HTTPS | ||
| secure=True, # TODO: Set to True in production with HTTPS | ||
| samesite="Lax", # TODO: Set to 'Lax' in production with HTTPS or 'None' for cross-site |
Copilot
AI
May 18, 2025
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 inline comment for samesite suggests alternative configurations; consider clarifying the intended production setup to avoid ambiguity.
| error={inputText.length > 11999} | ||
| helperText={inputText.length > 11999 ? "Input too long, max 12000 length supported" : ""} |
Copilot
AI
May 18, 2025
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.
[nitpick] Consider defining a constant for the maximum input length instead of using the magic number 12000 to improve maintainability.
| error={inputText.length > 11999} | |
| helperText={inputText.length > 11999 ? "Input too long, max 12000 length supported" : ""} | |
| error={inputText.length > MAX_INPUT_LENGTH - 1} | |
| helperText={inputText.length > MAX_INPUT_LENGTH - 1 ? `Input too long, max ${MAX_INPUT_LENGTH} length supported` : ""} |
|
amankrs21
left a comment
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.
All okay.



release-3.1.0