Move issues #1695 and #1694 back into the mdn/sprints or mdn/data repo

mdn / sprints

Archived: MDN Web Docs issues are tracked in the content repository.

https://github.com/mdn/content

Creative Commons Zero v1.0 Universal

151 stars 144 forks source link

Move issues #1695 and #1694 back into the mdn/sprints or mdn/data repo #3973

Closed ExE-Boss closed 3 years ago

ExE-Boss commented 3 years ago

@Elchi3 moved issues #1695 and #1694 from here into mdn/kumascript#1378 and mdn/kumascript#1379, but they should’ve been kept here (or moved to @mdn/data), because mdn/kumascript has now been archived, but #1695 is still unresolved, as @mdn/data still has outdated and missing:

InterfaceData.json (tracked in: #1694)
GroupData.json
SpecData.json (PR https://github.com/mdn/data/pull/397)
SVGData.json

Since @mdn/data is used by @mdn/yari, these issues still apply.

Elchi3 commented 3 years ago

Hey @ExE-Boss good to here from you again! I guess alternatively we can always file new issues and refer to old / archived ones as needed. I don't seem to be able to move this back.

ExE-Boss commented 3 years ago

@Elchi3 The @mdn/kumascript repository would need to be temporarily un‑archived.

chrisdavidmills commented 3 years ago

I think filing a new issue on yari will be best here. Bear in mind that eventually we'll get rid of KS macros, so this issue would be about moving the data files into Yari and making use of them in whatever way would make sense for a new feature set.