能增加推荐归因吗?
- Dominant language
- Go
- Stars
- 9.8k
- Forks
- 912
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 9
Description
**Is your feature request related to a problem? Please describe.**
getRecommend接口只返回了item_id,这导致很难做推荐归因
**Describe the solution you'd like**
希望getRecommend接口能够返回reason(recommender)和score
**Describe alternatives you've considered**
考虑过分别调用不同recommender的接口接口,但是那样会绕过CTR计算
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start by locating the getRecommend API entry point and tracing how recommendations pass through CTR calculation. Determine where item_id responses are assembled and how recommender attribution and scores are represented; done means the API exposes reason/recommender and score without bypassing CTR, with coverage for the response behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend-api-design, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100