multi-textarea data model keyed on (url, timestamp)
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 重構
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 領域
- frontend
研究方向
首先追蹤現有的 Spot datatype，以及 issue 中描述的目前 textarea-enhancement flow。將草稿的識別與還原方式與提議的 URL/timestamp schema 進行比較；完成的標準是專案已就用於保留與匹配多個 textarea 草稿的通用模型達成共識。
由索引模型根據 Issue 內容生成。
描述
As the code stands, there is a Spot datatype. It represents the abstract concept of where a single textarea is. e.g.
- appending the 2nd comment on issue 4
- appending the 3rd comment on issue 4
- pros: we have enough data to recreate the draft completely in the browser, and also enough data to tell if it was submitted or not
- cons:
- a lot of manual work for each place that we handle
- ambiguity around things like the
issues/newurl. You might have multiple unsubmitted drafts in progress, they don't have server-side IDs yet, what should their spot be? Inevitably it gets tied to the time that the tab happened to open, in which case why bother with the complexity of defining the "abstract place where a comment is" if you end up just doingtimestamp, URLpairs?
This approach really falls down for complex multi-form things, such as this:
It would be really painful to lose the drafts in those textboxes, but it's also impossible to make a spot for each textfield in every issue/PR template that might be out there.
Another approach is this:
- anytime a textarea gets added or removed, trigger a refractory state that waits until there's been no changes for 500ms
- when that refactory period times out (the textareas have settled), the Spot is defined as:
- primary key: (url, timestamp)
- schema: list of textareas and their labels, as best we can tell in a generic way
- title and icon: pulled from the tab by default
- cons: most of the time, this is not enough data to reopen the tab for the user
- pros:
- if the user has opened a tab manually, we can find which saved drafts fit that schema
- textareas can be enhanced by default, versus right now where they are enhanced only iff we have built an enhancer for that specific box
- 主要語言
- HTML
- 星號
- 58
- 分支
- 0
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
diffplug/gitcasso 的其他 Issue
-
Jukebox gap未關閉
難度 5/5 一週以上 新手友好度 10/100
-
Allow toggling syntax highlighting on/off for the page from a right click on the textarea/similar未關閉enhancement
難度 4/5 3-5 天 新手友好度 45/100
-
bug
難度 3/5 1-2 天 新手友好度 45/100
-
enhancement
難度 5/5 一週以上 新手友好度 20/100
-
enhancement
難度 5/5 一週以上 新手友好度 32/100
查看 diffplug/gitcasso 的全部 Issue
相似的 Issue
-
awaiting-response bug needs-triage
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 3 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
capricorn86/happy-dom#2484 ·
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
siyuan-note/siyuan#20430 · 1 則留言 ·
維護者通常 1 天內回覆
-
area:space-accuracy good first issue help wanted track:data
難度 2/5 1-3 小時 新手友好度 72/100
Sara-Managed-Projects/space-radar#898 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 68/100
LanternOps/breeze#8360 ·
維護者通常 1 天內回覆