GoogleChrome / GoogleChrome/webstatus.dev
[ENHANCEMENT] "Incorrect data" steps are unclear for Web DX Features
- Dominant language
- Go
- Stars
- 254
- Forks
- 62
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 64
Description
**Is your feature request related to a problem? Please describe.**
The "incorrect data" issue template asks contributors to "verify that the data displayed on webstatus.dev is different from the data in the original source".
This includes:
> - [ ] **Baseline Status, Browser Availability, Feature Groups, Feature Snapshots:**
> Check the [Web DX Features repository](https://github.com/web-platform-dx/web-features)
However, following that link, there's no obvious way to see what data `web-features` currently has to be able to determine whether there's a difference between `webstatus.dev` and `web-features`.
https://github.com/web-platform-dx/web-features/issues/541 is an old issue about visualising the results, but the last comment there is about the previous visualisation work being archived in favour of `webstatus.dev`.
Am I meant to download the NPM package and start digging through the JSON files? Is that what is asked of people filing issues against this repo?
**Describe the solution you'd like**
Guidance on what is expected before reporting a data issue; the guidance for wpt.fyi and BCD is simple enough with easy enough places to view the data, but it is much less clear for web-features. Making people dig through JSON files from an NPM package doesn't seem particularly friendly to people reporting issues.
**Describe alternatives you've considered**
`webstatus.dev` giving the context of "why" something is not available.
**Additional context**
N/A
Contributor guide
Assessment
This issue has not been assessed yet.