anandthakker / anandthakker/doiuse

Using MDN Data

未關閉
#163 1 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
JavaScript
星號
1.3k
分支
57
PR 合併指標
30 天內沒有已合併 PR

描述

Not all features are in the caniuse database (e.g. #161). So, we have to use MDN data during detection somehow. I'm just not sure how yet, so I'm gonna dump my thoughts here. Open to any and all thoughts, feelings, comments, and etc. There's definitely more options than just these :P

### Option 1: Use MDN for detection instead of caniuse. Quite a bit of work, but potentially a clean solution.
Pros:
- More CSS features are tracked
- Data includes information about prefixes
- Data has more robust partial support info
- Could potentially reduce the amount of boilerplate code needed for detection (in `data/features`)

Cons:
- lot of work

### Option 2: Convert any missing MDN data into caniuse's format and pretend it exists in caniuse-lite
Pros:
- Gets us the new features from MDN with less effort (probably)

Cons:
- Both datasets use a different format, and using them together could get a bit tricky. (e.g we'd have to dedupe entries, MDN compat entries are sometimes split out by value, etc.)
- Potentially more work to maintain.
- We'd still need MDN data to check for partial support & prefixes anyway

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。