想 propose 一個網站上「修改重發」回應的功能。
過去針對「編輯回應」有這些討論：
https://g0v.hackmd.io/OC7BneJ3TEGJHge1hWV-0w#%E8%A8%8E%E8%AB%96%EF%BC%9A%E8%AE%93%E4%BD%9C%E8%80%85%E8%83%BD%E7%B7%A8%E8%BC%AF%E5%9B%9E%E6%87%89 （天啊 2020 年）
還開了
一張票想要改 API，不外乎就是要解決
• 回應會被自己、被別人加到不同訊息下，此狀況下什麼樣的編輯算合理？
• 編輯後，針對舊文字的 feedback 怎麼辦？
因此，現在的 status quo 就是請使用者刪掉重發，這樣最單純。
我覺得比起「編輯」，其實更容易做的是把「修改重發」自動化，也就是針對現有回應做出「更動」後，系統其實不會動原有的回應，而是
• 新增新的回應
• 把新的回應加到原有回應連結的訊息上（僅限作者自己加的）
• 把原有回應刪除（僅限作者自己加的）
也就是現在查核協作者可以自行操作的動作，改成一鍵完成這樣。UX 細節如下：
• 回應作者在任何自己撰寫的回應上點擊「修改重發」，會被導向到該 reply 的 detail 頁面。
• reply detail 新增編輯模式，可修改「我認為」分類、內文與出處。
• 送出按鈕上面的用語為「修改重發」，前面說明文字簡述說，修改後的文案會同時套用到自己所連結的可疑訊息，也就是下方「此查核回應尚被用於以下的可疑訊息」列出的訊息中，由自己加的那些。
• 按下「修改重發」後，跳出彈窗列出那些會被套用的網傳訊息，以及確認按鈕。
• 按下確認後，彈窗顯示套用的進度，以及往新回應 detail 頁面的連結。
以上功能都可以用現有 API 做到，不用開新的欄位，只要改 rumors-site。
g0v.hackmd.io
20200715 會議記錄 - HackMD
#184 UpdateReply API and replyUpdateBlocker field for reply
As discussed in <https://g0v.hackmd.io/@mrorz/cofacts-meeting-notes/%2F%40mrorz%2Fr1dQQZbmU|20200212 meeting>, we want to allow editor to edit their reply when
• The reply is only used by the editor itself (the author should know the impact of the edit)
• The reply has not yet received any feedback (the edit should now invalidate user's feedbacks)
We plan to add 1 mutation API, and one new field to `Reply` type for this:
"""
The reason why the editor cannot edit
"""
enum ReplyUpdateBlocker {
NOT_AUTHORIZED # Not logged in or not the author of reply
HAS_FEEDBACK
USED_BY_OTHER_EDITORS
}
type Reply {
"""
The reason why the current user cannot edit this reply. null if the current user can edit.
The blockers are determined in the following order:
(1) current user is the author or not
(2) `positiveFeedbackCount` and `negativeFeedbackCount` are both 0 or not
(3) all normal article-reply to this article are by the current author or not
"""
updateBlocker: ReplyUpdateBlocker
}
mutation {
"""
Updates reply text, type & reference when
(1) current user is the author
(2) `positiveFeedbackCount` and `negativeFeedbackCount` are both 0
(3) all normal article-reply to this article are by the current author
"""
UpdateReply(
replyId: String!
text: String
type: ReplyTypeEnum
reference: String
waitForHyperlinks: Boolean = false
) {
""'
The reply after update. `null` when update is not successful
"""
reply: Reply
"""
The reason why update fails. null when can update.
"""
blocker: ReplyUpdateBlocker
}
}
"all normal article-reply to this article are by the current author" can be achieved by loading article-reply of a reply using <https://github.com/cofacts/rumors-api/blob/master/src/graphql/dataLoaders/articleRepliesByReplyIdLoaderFactory.js|`articleRepliesByReplyIdLoader`> and check each article-reply's author ID.
FETS 
1
LINE TODAY 
facebook.com 
