feat: 接入计划广场后端主链路
This commit is contained in:
@@ -4,6 +4,8 @@ import (
|
||||
"log"
|
||||
|
||||
"github.com/LoveLosita/smartflow/backend/bootstrap"
|
||||
legacydao "github.com/LoveLosita/smartflow/backend/dao"
|
||||
"github.com/LoveLosita/smartflow/backend/services/taskclassforum/adapter"
|
||||
forumdao "github.com/LoveLosita/smartflow/backend/services/taskclassforum/dao"
|
||||
forumrpc "github.com/LoveLosita/smartflow/backend/services/taskclassforum/rpc"
|
||||
forumsv "github.com/LoveLosita/smartflow/backend/services/taskclassforum/sv"
|
||||
@@ -20,10 +22,14 @@ func main() {
|
||||
log.Fatalf("failed to connect taskclassforum database: %v", err)
|
||||
}
|
||||
|
||||
// 1. 当前阶段只启动计划广场自身 RPC 壳。
|
||||
// 2. TaskClass legacy adapter 会在第三步业务主链路接入,避免现在抢改 task 模块。
|
||||
// 3. 未实现的业务方法会明确返回 Unimplemented,而不是伪装成可用能力。
|
||||
svc := forumsv.New(forumsv.Options{DB: db})
|
||||
// 1. 复用同一个 DB 句柄装配 legacy TaskClass DAO,避免本轮抢改 task-class 模块。
|
||||
// 2. 计划广场只通过快照端口读取和创建 TaskClass,不直接写 schedule。
|
||||
// 3. 后续 task-class 独立成服务后,只替换这里的 adapter 注入点。
|
||||
taskClassPort := adapter.NewLegacyTaskClassAdapter(legacydao.NewTaskClassDAO(db))
|
||||
svc := forumsv.New(forumsv.Options{
|
||||
DB: db,
|
||||
TaskClassPort: taskClassPort,
|
||||
})
|
||||
forumrpc.Start(forumrpc.ServerOptions{
|
||||
ListenOn: viper.GetString("taskclassforum.rpc.listenOn"),
|
||||
Timeout: viper.GetDuration("taskclassforum.rpc.timeout"),
|
||||
|
||||
Reference in New Issue
Block a user