Ptt-official-app/Ptt-backend

[主線] [PTT] 實作上下箭頭推文

Open

#210 opened on May 30, 2021

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Go (65 forks)auto 404
help wanted

Repository metrics

Stars
 (211 stars)
PR merge metrics
 (PR metrics pending)

Description

實作細節 / Details of Implement

Quote from Pichu:

在放入 user01 Access Token 的情況下，發出一篇文章，user02 可以用 「↑」進行推文，評價數要加一，user02第二次用 ↑ 推文時評價數不變 接著user02 用 「↓」推文時原先的上箭頭推文被刪去，評價數減一（收回），第二次用 ↓ 推文時評價數減一，第三次用↓推文時評價數不變 在放入 user01 Access Token 的情況下，發出一篇文章，user01 用 「↑」進行推文，評價數不變 （自己不能推自己）

  • 修改usecase /article.go
    • 增加類似UpdateUsefulness function，以模仿stackoverflow或reddit
  • 在repository/article.go中新增Usefulness struct，與後端gobbs對接
  • 在delivery/http新增route_update_usefulness.go處理http routing
  • 可能會有權限問題需要處理
  • 對應測試需要撰寫

期程 / Schedule

  • 討論時間： 兩周
  • 實作時間： 兩周
  • 確認時間： 兩周

備註

  • 目前Google doc那裏還沒更新
  • 子issue需要協助開立

Contributor guide

Research direction
Study the existing article usecase, repository, and HTTP delivery structure. Then add a new UpdateUsefulness function in usecase/article.go, create a Usefulness struct in repository/article.go with methods to interact with the backend (gobbs), add a new route in delivery/http (route update usefulness.go), and handle permission logic (prevent self upvote and handle duplicate votes). Write corresponding tests.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoREST API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50