News for hackers. Stuff that matters.

A comment on Caniuse and MDN compatibility data collaboration. Parent comment

Re:Caniuse and MDN compatibility data collaboration by myfonj on Wednesday September 11, 2019 @06:52AM (#20938590)
It seemed quite straightforward to me last time I wanted to update something: there is boilerplate (schema [0]) JSON for feature / subfeature that lists all browsers in current documentation set with `{"version_added": null}` meaning "I don't know if given browser supports this feature" [1]. It's probably fine to introduce feature with completely unknown support just to ease future updates. I'm not sure if introduced feature should be in some advanced standardization process stage or not.

For bugs and details in implementations you can use `{versoin_added: true, notes: ["not in conditions described in <a href='...'>some bugreport</a>"]}` [2].

[0] https://github.com/mdn/browser-compat-data/blob/4f34583ab491... [1] https://github.com/mdn/browser-compat-data/blob/master/schem... [2] https://github.com/mdn/browser-compat-data/blob/master/schem...

[ Parent | on HN ]
Re:Caniuse and MDN compatibility data collaboration by a2sheppy on Thursday September 12, 2019 @06:10PM (#20956999)
In order to help ensure that data gets filled out and we don't wind up with strays, we stopped allowing the null value for a version, so you can no longer indicate "unknown" as support level for a feature in BCD's data store. If you don't know the values, you can submit a patch but someone will have to add the missing data before it can be accepted, as it will fail the automated testing without data for every browser supported by the JSON.
[ Parent | on HN ]
Re:Caniuse and MDN compatibility data collaboration by greggman2 on Thursday September 12, 2019 @11:09PM (#20958835)
that seems in scalable and adds such a burden to adding data that it will have the unintended consequence of discouraging participation.

I only have a dataset of 1 but it seems like it would be useful data for devs to see so they know they can not use features X, Y, and Z if they want to be cross platform because of bugs in specific implementation but given I can't add the data without going through all the browsers, given that "unknown" is not the right label for conforming browsers, and given that I don't have time to dig up proof the other browsers conform I opted to remove my pull request

[ Parent | on HN ]
Re:Caniuse and MDN compatibility data collaboration by myfonj on Friday September 13, 2019 @06:27AM (#20960765)
That's sad. While understandable if you were overwhelmed with poor half-hearted "stray" PRs, still I doubt that any random developer will sift trough open PRs to add his two cents of knowledge about "invisible" (unpublished) feature to make it complete for acceptation. Seeing blanks-to-be-filled directly in public documentation feels far more motivating for quick ("wiki") edit.
[ Parent | on HN ]