Update workflow
- 主要語言
- JavaScript
- 星號
- 30
- 分支
- 7
- PR 合併指標
- 30 天內沒有已合併 PR
描述
Currently the flow is like this.
In `WebembedHandler`
1. Tries to detect provider from the list and run `oembed.fetch` of `oembed` lib
2. If above fails, it then tries to fetch data manually either from parent class Platform or a customClass which respect additional props support in providers list
3. If either of them fail, it will generate a fallback
There is a lot of scope to refactor this to make it work faster during this process.
For example, we can make only one request to final targetURL and reuse it from step 1 to 3.
Feel free to suggest alternative ideas
貢獻指南
這個儲存庫沒有索引到貢獻指南
研究方向
首先,追蹤 WebembedHandler 經過 oembed 函式庫、Platform、customClass 和 providers 清單的流程。測量在三個 fallback 階段中對 targetURL 發出請求的方式,並記錄已達成共識的重構方案。當流程在避免冗餘請求的同時保留 provider 偵測和 fallback 行為時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript
- 領域
- backend
- Issue 類型
- 重構
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100