Merged
Conversation
Bumps [github.com/gin-contrib/cors](https://github.com/gin-contrib/cors) from 1.4.0 to 1.6.0. - [Release notes](https://github.com/gin-contrib/cors/releases) - [Changelog](https://github.com/gin-contrib/cors/blob/master/.goreleaser.yaml) - [Commits](gin-contrib/cors@v1.4.0...v1.6.0) --- updated-dependencies: - dependency-name: github.com/gin-contrib/cors dependency-version: 1.6.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [github.com/jackc/pgx/v5](https://github.com/jackc/pgx) from 5.2.0 to 5.5.4. - [Changelog](https://github.com/jackc/pgx/blob/master/CHANGELOG.md) - [Commits](jackc/pgx@v5.2.0...v5.5.4) --- updated-dependencies: - dependency-name: github.com/jackc/pgx/v5 dependency-version: 5.5.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…m/jackc/pgx/v5-5.5.4 chore(deps): bump github.com/jackc/pgx/v5 from 5.2.0 to 5.5.4
…m/gin-contrib/cors-1.6.0 chore(deps): bump github.com/gin-contrib/cors from 1.4.0 to 1.6.0
Refactor/architecture optimization
There was a problem hiding this comment.
Pull Request Overview
This PR implements a comprehensive modernization and optimization of the FileCodeBox admin interface, focusing on improved UI/UX, configuration management, and system integrity.
- Modern Material Design-inspired admin interface with responsive layout and dark/light theme support
- Enhanced configuration handling with improved data normalization and better error management
- Strengthened build system with consistent versioning and cross-platform compatibility
Reviewed Changes
Copilot reviewed 31 out of 32 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| themes/2025/admin/js/main.js | Enhanced UI logic with theme support, mobile navigation improvements, and better configuration handling |
| themes/2025/admin/js/config-simple.js | Added configuration normalization and improved type handling for opacity and other UI settings |
| themes/2025/admin/index.html | Complete admin interface redesign with modern sidebar navigation, responsive metrics, and improved semantic structure |
| themes/2025/admin/css/admin-modern.css | New comprehensive CSS framework implementing modern design system with variables, responsive breakpoints, and consistent component styling |
| scripts/release.sh, scripts/cross-build.sh, scripts/build.sh | Updated build scripts to use correct version injection paths |
| main.go | Updated API version number to 1.8.2 |
| internal/utils/disk_windows.go, internal/utils/disk_unix.go | Added cross-platform disk usage utilities with proper build constraints |
| internal/static/assets.go | Enhanced theme resolution system with fallback mechanisms and improved error handling |
Comment on lines
+48
to
+50
| const clone = typeof structuredClone === 'function' | ||
| ? structuredClone(config) | ||
| : JSON.parse(JSON.stringify(config)); |
There was a problem hiding this comment.
Using JSON.parse(JSON.stringify()) as a fallback for deep cloning can be slow for large objects and doesn't handle functions, dates, or other complex types. Consider using a proper deep clone utility or implementing a more robust fallback.
Comment on lines
+284
to
+286
| if (value === '') return null; | ||
| const num = parseFloat(value); | ||
| return Number.isNaN(num) ? null : num; |
There was a problem hiding this comment.
[nitpick] The getFieldValue function has inconsistent return types - returning null for float type but 0 for number type when parsing fails. Consider standardizing the fallback behavior or documenting this difference clearly.
Suggested change
| if (value === '') return null; | |
| const num = parseFloat(value); | |
| return Number.isNaN(num) ? null : num; | |
| if (value === '') return 0; | |
| const num = parseFloat(value); | |
| return Number.isNaN(num) ? 0 : num; |
Comment on lines
+44
to
+56
| func firstExistingThemeDir(cfg *config.ConfigManager) string { | ||
| for _, candidate := range themeCandidates(cfg) { | ||
| if filepath.IsAbs(candidate) { | ||
| if themeDirExists(candidate) { | ||
| return candidate | ||
| } | ||
| continue | ||
| } | ||
| if themeDirExists(candidate) { | ||
| return candidate | ||
| } | ||
| } | ||
| return defaultThemeDir |
There was a problem hiding this comment.
[nitpick] The logic for checking absolute vs relative paths is duplicated. Consider extracting this into a helper function or simplifying the logic to reduce code duplication.
zy84338719
added a commit
that referenced
this pull request
Sep 24, 2025
Merge pull request #10 from zy84338719/main
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.