4d9a5c4d30
后端： 1. 阶段 4 active-scheduler 服务边界落地，新增 `cmd/active-scheduler`、`services/active_scheduler`、`shared/contracts/activescheduler` 和 active-scheduler port，迁移 dry-run、trigger、preview、confirm zrpc 能力 2. active-scheduler outbox consumer、relay、retry loop 和 due job scanner 迁入独立服务入口，gateway `/active-schedule/*` 改为通过 zrpc client 调用 3. gateway 目录收口为 `gateway/api` + `gateway/client`，统一归档 userauth、notification、active-scheduler 的 HTTP 门面和 zrpc client 4. 将旧 `backend/active_scheduler` 领域核心下沉到 `services/active_scheduler/core`，清退旧根目录活跃实现，并补充 active-scheduler 启动期跨域依赖表检查 5. 调整单体启动与 outbox 归属，`cmd/all` 不再启动 active-scheduler workflow、scanner 或 handler 文档： 1. 更新微服务迁移计划，将阶段 4 active-scheduler 标记为首轮收口完成，并明确下一阶段进入 schedule / task / course / task-class
29 lines
1.2 KiB
Go
29 lines
1.2 KiB
Go
package userauthapi
|
|
|
|
import (
|
|
gatewaymiddleware "github.com/LoveLosita/smartflow/backend/gateway/middleware"
|
|
rootmiddleware "github.com/LoveLosita/smartflow/backend/middleware"
|
|
"github.com/LoveLosita/smartflow/backend/pkg"
|
|
"github.com/LoveLosita/smartflow/backend/shared/ports"
|
|
"github.com/gin-gonic/gin"
|
|
)
|
|
|
|
// RegisterRoutes 把 user/auth HTTP 入口挂到 gateway 路由组。
|
|
// 职责边界：
|
|
// 1. 只注册 /user 下的边缘路由，不关心其它业务域路由；
|
|
// 2. 登录、注册、刷新 token 只做请求转发；登出需要先经过 access token 边缘鉴权；
|
|
// 3. 限流仍复用当前通用中间件，后续若 gateway 独立成包，可再整体下沉。
|
|
func RegisterRoutes(apiGroup *gin.RouterGroup, handler *UserHandler, authClient ports.AccessTokenValidator, limiter *pkg.RateLimiter) {
|
|
if apiGroup == nil || handler == nil {
|
|
return
|
|
}
|
|
|
|
userGroup := apiGroup.Group("/user")
|
|
{
|
|
userGroup.POST("/register", handler.UserRegister)
|
|
userGroup.POST("/login", handler.UserLogin)
|
|
userGroup.POST("/refresh-token", handler.RefreshTokenHandler)
|
|
userGroup.POST("/logout", gatewaymiddleware.JWTTokenAuth(authClient), rootmiddleware.RateLimitMiddleware(limiter, 20, 1), handler.UserLogout)
|
|
}
|
|
}
|