feat: 0.8 version #1172
Merged
feat: 0.8 version #1172
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Apple\Apple <[email protected]>
This reverts commit 74572ab.
Signed-off-by: Apple\Apple <[email protected]>
Signed-off-by: Apple\Apple <[email protected]>
…ame in the HeaderBar during loading
…the login session expired
…under the Sidebar
The `handleNavLinkClick` function in `HeaderBar.js` was previously forcing the sidebar to be visible for all non-'home' navigation links on non-mobile devices. This interfered with the intended logic in `StyleContext` which controls sidebar visibility based on the current route. This commit modifies `handleNavLinkClick` to: - Only apply specific style dispatches (setting inner padding and sider to false) for the 'home' link, which may have unique layout requirements. - Remove the logic that unconditionally set sidebar visibility and inner padding for other navigation links. - Continue to close the mobile menu загрязнения (`setMobileMenuOpen(false)`) on any nav link click. This change ensures that `StyleContext` is the single source of truth for determining sidebar visibility based on the route, resolving an issue where clicking a non-console link Pferde (e.g., 'Pricing', 'About') would incorrectly display the sidebar, especially when the link was clicked Pferde a second time while already on that page.
…sole link Previously, when an unauthenticated user clicked the "Console" navigation link, the application would first attempt to navigate to '/console'. This would then trigger a redirect to '/login', causing a brief flicker between the two pages. This commit modifies the `renderNavLinks` function in `HeaderBar.js` to proactively check the user's authentication status. If the user is not logged in and clicks the "Console" link, the navigation target is directly set to '/login', avoiding the intermediate redirect and eliminating the flickering effect.
This commit introduces a new component `AuthRedirect` which checks if a user is already logged in. If the user is logged in and attempts to access the /login or /register pages, they will be redirected to the /console page. Otherwise, the respective authentication form (Login or Register) will be rendered. The `App.js` file has been updated to utilize this new `AuthRedirect` component for the /login and /register routes.
When resizing from medium screens to desktop view in the console section, the sidebar previously failed to appear automatically. This commit fixes the issue by simplifying the logic to always show the sidebar when in desktop mode and in console pages, regardless of previous screen size.
fix: 修复复制多选令牌按钮的文本
Feat: 2.5-pro thinkingBudget
Fix: Correctly relay FunctionResponse content for Gemini API
Fix: 更新2.5 pro的思考预算范围
Improve the model list section in PersonalSetting component with the following enhancements: - Add category-based tabs for filtering models by provider (OpenAI, Anthropic, etc.) - Implement skeleton loading states using Semi UI components - Add empty state illustrations when no models are available - Use Semi UI design tokens for consistent styling - Optimize display for both expanded and collapsed model lists - Simplify some button text labels for better UI consistency
…code organization This commit improves the codebase structure by: - Moving all inline styles from SiderBar.js to CSS classes in index.css - Organizing CSS with clear section comments for better maintainability - Removing unused imports and components - Improving sidebar design with cleaner styling and consistent color management - Restructuring CSS to group related styles together - Adjusting sidebar width from 200px to 180px - Replacing Text components with semantic divs for group labels - Creating a color management function for sidebar icons
- Consolidate 8 individual stat cards into 4 grouped cards: * Account Data (Current Balance, Historical Consumption) * Usage Statistics (Request Count, Statistics Count) * Resource Consumption (Statistics Quota, Statistics Tokens) * Performance Metrics (Average RPM, Average TPM) - Add gradient header backgrounds with white text for card titles: * Blue gradient for Account Data * Green gradient for Usage Statistics * Yellow gradient for Resource Consumption * Pink gradient for Performance Metrics - Implement mini trend charts using real API data: * Replace mock data with actual time-series data from API * Hide x and y axes to show pure trend lines * Display trends only for metrics with available historical data * Remove trend charts for Current Balance, Historical Consumption, and Request Count - Merge model analysis charts into single card: * Combine "Model Consumption Distribution" and "Model Call Count Ratio" * Use responsive grid layout (vertical on mobile, horizontal on desktop) * Update card title to "Model Data Analysis" - Optimize chart configurations: * Hide axes, legends, and tooltips for mini trend charts * Maintain color consistency between metrics and trend lines * Improve performance by processing all trend data in single API call
Fix background color rendering issues for notification bell, theme toggle, and language switcher buttons in the header bar. These buttons were missing !important declarations in their CSS classes, causing inconsistent styling across different devices where other styles could override the intended background colors. Changes: - Add !important to background color classes for notification button - Add !important to background color classes for theme toggle button - Add !important to background color classes for language switcher button - Ensure all header action buttons now have consistent styling matching the user avatar dropdown button This resolves visual inconsistencies where these buttons would appear without proper background colors on certain devices or screen configurations.
Fix dark mode background color rendering issue in the footer component where the custom dark background color (#1C1F23) was not being applied consistently across different devices due to missing !important declaration. Changes: - Add !important to dark mode background color class in footer - Change `dark:bg-[#1C1F23]` to `dark:!bg-[#1C1F23]` - Ensure footer dark mode styling is not overridden by other CSS rules This resolves visual inconsistencies where the footer would not display the intended dark background color in dark theme mode on certain devices or screen configurations.
Add fallback display value when system_name is not available or empty. This ensures the homepage title always shows meaningful content instead of being blank when the system name hasn't been configured or fails to load. - Update Home component to display "New API" as default when statusState?.status?.system_name is falsy - Improves user experience by preventing empty title display
Update Footer component to use semantic color variables for better theme integration: - Replace hardcoded background color with semi-color-bg-2 for theme consistency - Update text colors to use semantic variables (semi-color-text-0, semi-color-text-1) - Replace hardcoded link colors with semi-color-primary for brand consistency - Add hover effects with smooth transitions for better user experience - Keep logo container background as gray-800 for visual stability This ensures the footer adapts properly to different theme modes while maintaining good readability and visual consistency across the application.
Fix the last column (operation/detail columns) to the right side across all table components to improve user experience and ensure important actions remain visible during horizontal scrolling. Changes: - ChannelsTable.js: Fix operation column to right - UsersTable.js: Fix operation column to right - TokensTable.js: Fix operation column to right - RedemptionsTable.js: Fix operation column to right - LogsTable.js: Fix details column to right - MjLogsTable.js: Fix fail reason column to right - TaskLogsTable.js: Fix fail reason column to right All tables now have their rightmost column fixed using Semi Design's `fixed: 'right'` property, ensuring critical information and actions are always accessible regardless of table scroll position.
Enhance table scrollbar visual design with lighter and thinner styling for better user experience. Changes: - Add custom scrollbar styling for .semi-table-body - Set scrollbar dimensions to 6px width/height - Apply lighter color using rgba(var(--semi-grey-2), 0.3) with 30% opacity - Add hover effect with 50% opacity for better interaction feedback - Use 2px border radius for smoother appearance - Keep scrollbar track transparent for clean look - Utilize Semi Design color variables for theme consistency The new scrollbar design provides a more elegant and less intrusive horizontal scrolling experience across all data tables.
…rization - Extended OpenAI model filter to include o1, o3, and o4 series models - Updated model categorization logic to properly classify reasoning models - Ensures all OpenAI model variants (o1-mini, o1-preview, o3, o4, etc.) are correctly grouped under OpenAI category - Maintains backward compatibility with existing GPT and other OpenAI model series
Implement rowExpandable property to control which rows can be expanded in the logs table. Rows are now only expandable when they have actual expand data content, preventing empty expansion sections from being displayed to users. - Add rowExpandable function to check if expandData exists and has content - Improve user experience by hiding expand functionality for rows without details - Maintain existing expand behavior for rows with valid expansion data
Previously, the notice modal would automatically show every day even when the notice content was empty, causing unnecessary user interruption. This commit modifies the logic to: - Check notice content before showing the modal - Only display the modal when notice content exists and is not empty - Add proper error handling to prevent modal showing on API failures - Improve user experience by avoiding empty notice interruptions Changes: - Modified useEffect in Home component to fetch notice content first - Added API call to /api/notice before setting noticeVisible state - Added try-catch block for graceful error handling - Only show modal when notice data is truthy and non-empty after trimming
Standardize the scrollbar appearance of semi-sidesheet-body to match the existing semi-table-body style. This change: - Sets scrollbar width to 6px - Applies light gray color (rgba(var(--semi-grey-2), 0.3)) - Adds subtle hover effect - Uses 2px border radius for consistency - Improves overall UI cohesion across components
The Table component in LogsTable.js was previously showing expand icons for all rows, even those without any expandable content. This led to a confusing UX where users could click to expand rows but would see empty content. This commit adds the `rowExpandable` property to the Table configuration to ensure that only rows with actual expandable content show the expand icon and can be expanded. The function checks if each record has corresponding data in the expandData object before allowing it to be expanded.
Set a minimum width of 200px for progress components in both MjLogsTable.js and TaskLogsTable.js to ensure consistent display and prevent them from becoming too narrow when table resizes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.