feat(feedback): feat(feedback): add ListFeedback service - #340
Merged
Conversation
wastefi
requested review from
a team,
jiuxia211,
mutezebra and
ozline
as code owners
October 6, 2025 13:34
Codecov Report❌ Patch coverage is @@ Coverage Diff @@
## main #340 +/- ##
========================================
+ Coverage 5.24% 5.64% +0.39%
========================================
Files 255 270 +15
Lines 31091 34397 +3306
========================================
+ Hits 1630 1940 +310
- Misses 29362 32325 +2963
- Partials 99 132 +33
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 3 files with indirect coverage changes 🚀 New features to boost your workflow:
|
FantasyRL
requested changes
Oct 7, 2025
FantasyRL
approved these changes
Oct 7, 2025
Member
|
@FantasyRL 老大我日你大坝,微信聊天都给删干净了吗怎么来了个 approve,速速再看 2 遍 |
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.
自查 PR 结构
PR 标题符合这个格式: <type>(optional scope): <description>
此 PR 标题的描述以用户为导向,足够清晰,其他人可以理解。
我已经对所有 commit 提供了签名(GPG 密钥签名、SSH 密钥签名)
这个 PR 属于强制变更/破坏性更改
这个 PR 的类型是什么?
feat
这个 PR 做了什么 / 我们为什么需要这个 PR?
目前的福uu受众面相对较大,经常出现用户通过app内的飞书文档反馈bug。然而,飞书文档的反馈无法精准定位用户问题所在,简单的反馈表单无法满足回查所在,因此我们想要有一个内置的反馈系统。
这个pr目前提供了最简单的CreateFeedback与GetFeedback的后端接口。同时,该功能与当前的模块定位都不太符合,因此还新建了一个oa模块。
(可选)这个 PR 解决了哪个/些 issue?
对 Reviewer 预留的一些提醒