layout 优化

[shenqidebaozi]

@Terry-Mao Layout 有几个优化

• [x] Usecase 需要定义在 biz 中；
• [x] Usecase 出入参为 DTO（解决以前模式里，service 传递 Usecase 参数过多的问题），Usecase 负责 DTO 到 DO 转换，反之亦然；
• [x] Usecase 只负责控制编排；
• [x] biz 的 errors 需要定义，可以不依赖 kratos，直接用标准库 errors.New，需要在 Usecase 转换成 kratos errors，需要思考下 mapping 映射
• [ ] 分页规范化
• [ ] field_mask示例
• [ ] 实现 book 示例

[tonybase]

• [ ] 分页规范化
• [ ] field_mask示例
• [ ] 实现 book 示例

[dosubot[bot]]

Hi, @shenqidebaozi! I'm Dosu, and I'm helping the kratos-layout team manage their backlog. I wanted to let you know that we are marking this issue as stale.

From what I understand, the issue titled "layout 优化" suggests several optimizations for the layout, including defining Usecase in biz, using DTO for Usecase input and output, and standardizing pagination. Tonybase has commented on the issue, suggesting tasks such as page standardization, field_mask examples, and implementing a book example.

It seems that Tonybase's suggestions address the optimizations mentioned in the issue.

Before we close this issue, we wanted to check with you if it is still relevant to the latest version of the kratos-layout repository. If it is, please let us know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.

Thank you for your contribution!