refactor: 把 /derivatives 的多源编排从 controller 搬进 usecase
为什么:原 controller handler 在 HTTP 层同时承担了 4 项 usecase 职责 (多源拼装、错误降级策略、limit 硬编码、响应结构组装),违反了 "controller 只做参数解析 + 调用 + 序列化" 的边界。等后续给衍生品加 缓存 / taker volume / 数据质量字段时,HTTP 层会持续变厚。 改动: - 新增 internal/usecase/market_query.go: MarketQueryUsecase.GetDerivatives() 并发拉 current funding/OI + 串行查历史 + 错误聚合为 warnings 返回 - /derivatives handler 退化到 4 行;MarketDeps / restapi.Deps 同步收窄 - /klines 保持直查 KlineRepo(thin query,G11 例外) - 新增 G11 守卫:grep "FundingRepo|OIRepo|LSRepo|TakerRepo" internal/controller 破坏性 API 变更(/derivatives 响应): - 删除 funding.error / openInterest.error - 新增顶层 warnings: []string 顶层 symbol / funding / openInterest / longShortRatio / takerBuySellVolume 保持。 harness 同步: - AGENTS.md §6 加 G11 grep - ai/project-map.md 加 market_query.go + /derivatives 数据流分支 - ai/task-templates.md T6 加"破坏性变体"分支(本次重构暴露了原假设过严) - ai/harness-health.md W1 记一次轻量验证 + 守卫数 10→11 验收: go build / go vet / G6 grep / G11 grep 全绿。
This commit is contained in:
@@ -58,6 +58,13 @@ func Run(cfg *config.Config, log *slog.Logger) error {
|
||||
log,
|
||||
)
|
||||
|
||||
queryUC := usecase.NewMarketQueryUsecase(
|
||||
binanceClient,
|
||||
fundingRepo,
|
||||
oiRepo,
|
||||
lsRepo,
|
||||
)
|
||||
|
||||
collector := worker.NewCollector(worker.Deps{
|
||||
MarketData: binanceClient,
|
||||
Derivatives: binanceClient,
|
||||
@@ -90,12 +97,9 @@ func Run(cfg *config.Config, log *slog.Logger) error {
|
||||
restapi.Register(fiberApp, restapi.Deps{
|
||||
Logger: log,
|
||||
MarketContext: contextUC,
|
||||
MarketQuery: queryUC,
|
||||
MarketData: binanceClient,
|
||||
Derivatives: binanceClient,
|
||||
KlineRepo: klineRepo,
|
||||
FundingRepo: fundingRepo,
|
||||
OIRepo: oiRepo,
|
||||
LSRepo: lsRepo,
|
||||
})
|
||||
|
||||
listenErr := make(chan error, 1)
|
||||
|
||||
Reference in New Issue
Block a user