New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split and merge syntaxes.json
into functions.json
and types.json
#670
Comments
It looks like this is your first issue. Welcome! 👋 One of the project maintainers will be with you as soon as possible. We appreciate your patience. To safeguard the health of the project, please take a moment to read our code of conduct. |
I missed when |
I found that So there're two ways to move forward:
|
Thank you for opening this issue, and sorry for the long waiting time. 🙏 Unfortunately, I'm not very familiar with mdn/data, so I must be missing some important context here. @yarusome As I understand, the combined The documented plan has been to deprecate this package in favor of w3c/webref, which is blocked by references to mdn-data in yari. Since this package is used a lot with 26 million weekly downloads, we need to have a very good reason for this breaking change. If all the data in mdn-data can be derived from w3c/webref (can it?), then it might make sense to publish mdn-data v3 such that it extracts the data from w3c/webref and merely presents it in the current format. But I'm not sure what the advantage of mdn-data's representation is in comparison to w3c/webref? |
@yarusome Can you please take a look at my previous comment? |
What information was incorrect, unhelpful, or incomplete?
syntaxes.json
contains data for both CSS functional notations and CSS types, but there already existfunctions.json
andtypes.json
for such data.I'm working on a script for diffing mdn/data and w3c/webref, and the existence of
syntaxes.json
would make the script less useful since this file increases the complexity of comparison bewteen the two data sources.What did you expect to see?
This file be split and merged into
functions.json
andtypes.json
.Incidentally,
functions.md
is not at all explaining the structure offunctions.json
, so it should be corrected as well.Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
I'll make a PR if this reorganization is agreed but no one does it, but that would be after I having finished writing and testing the script (probably in June).
The text was updated successfully, but these errors were encountered: