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