Dev=workflow si - #38
Closed
StardustSeemsInk wants to merge 3 commits into
Closed
Conversation
Member
Author
|
Wrong branch. |
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
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.
What does this PR do?
将Dashboard的后端逻辑分离为Core项目(和Core.Contract项目),并添加了Workflow相关的功能(包括BlockScript与蓝图,它们的互译与编译运行/debug模式运行,前端编辑器窗口与工作流库管理界面)。
This pull request introduces a comprehensive architectural plan and several code changes to support the separation of KitX Dashboard into distinct front-end and back-end components. The main focus is on decoupling business logic from UI, introducing new service providers, updating project dependencies, and laying out detailed documentation and migration strategies for the refactor.
Key changes:
Architectural Documentation & Planning
Detiled-Plan.md) outlining the current monolithic issues, what logic should be moved to the new backend (Core), what remains in the frontend, and a phased migration and refactor plan. This includes explicit file and class migration mapping, interface design, DI setup, and API/SignalR communication patterns.Separation-Plan.md) describing the new system structure, responsibilities of each part, migration steps, and new directory layout for both Core and Dashboard projects.Backend/Frontend Code Separation
PluginServiceProvider, a new class that acts as a bridge between the Dashboard and the plugin parser, providing methods to find plugins/connectors, send requests, and subscribe to plugin responses. This class encapsulates communication logic and error handling for plugin operations.PluginConnectorto include a static eventOnPluginResponsefor handling asynchronous plugin responses, and updated the command dispatch logic to trigger this event when a response with aRequestIdtag is received. [1] [2]Project & Model Updates
Kscript.CSharp.Parserproject, preparing the solution for future backend integration and scripting support. [1] [2]WorkflowCasemodel with a newScriptPathproperty to support referencing external script files for workflows.These changes provide a solid foundation for the planned front-end/back-end separation and enable scalable, maintainable growth of the KitX Dashboard platform.