feat(api): 封装JsonEditorTool为可调用的WebSocket API - 新增JsonApi类,管理多个JsonEditorTool实例 - 添加Tool和ToolData内部类,支持类和字段信息查询 - 实现WebSocket服务器,支持客户端连接和消息广播 - 设计WebSocketData、WebSocketDataType及DataType枚举,定义消息格式 - 实现消息内容自动解析与结构化处理 - 增加日志、错误、警告及调试信息的回调支持 - 兼容不同数据类型的输入输出处理逻辑 - 删除.gitignore中部分冗余文件忽略配置#29
Conversation
- 在 blank.yml 工作流中为构建任务添加 continue-on-error 选项 - 添加完整的首页 HTML 页面,包含 Mindustry IDE 的基本布局 - 实现项目启动、加载、导入、工具、设置等功能按钮 - 集成 Toast 通知系统和居中对话框系统 - 添加类搜索下拉框功能用于新建项目 - 实现项目列表管理和 CRUD 操作 - 添加工具列表和外部链接功能
- 移除多个类型定义JSON文件,包括Ability、Accelerator、ArmorPlateAbility等 - 删除无用的SVG图标资源admin.svg - 清理项目中遗留的application.properties文件 - 删除自动布局功能文档AUTO_LAYOUT_FEATURE.md - 彻底清理构建输出和资源目录下的类型定义文件 - 减少项目冗余文件,优化项目结构和维护成本
- 新增JsonApi类,管理多个JsonEditorTool实例 - 添加Tool和ToolData内部类,支持类和字段信息查询 - 实现WebSocket服务器,支持客户端连接和消息广播 - 设计WebSocketData、WebSocketDataType及DataType枚举,定义消息格式 - 实现消息内容自动解析与结构化处理 - 增加日志、错误、警告及调试信息的回调支持 - 兼容不同数据类型的输入输出处理逻辑 - 删除.gitignore中部分冗余文件忽略配置
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5e1fadf170
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| override fun onMessage(conn: WebSocket, message: String) { | ||
| println("收到消息: $message") | ||
| conn.send("Echo: $message") |
There was a problem hiding this comment.
Dispatch WebSocket messages to the API
For any client that connects to the new WebSocket server and sends one of the defined request types such as AllClass or AllField, onMessage currently only returns Echo: ... and never parses WebSocketData or calls ToolData/Tool, so the advertised callable WebSocket API cannot actually be used.
Useful? React with 👍 / 👎.
| - name: Build mod apk | ||
| run: bash ./gradlew assemble | ||
| continue-on-error: true |
There was a problem hiding this comment.
Stop swallowing build failures
In the release workflow, a failed bash ./gradlew assemble now continues to the artifact upload and release steps instead of failing the job immediately; when the APK build fails late or produces only partial outputs, the workflow can still publish a release without the expected APK, masking the broken build. The same pattern is also applied to the tool jar step below.
Useful? React with 👍 / 👎.
No description provided.