You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we had two customers seeking clarity on the major bump of our latest @webref/css, which I take as a signal we should be more explicit about these :) #688 (comment) mdn/yari#6913 (comment)
The text was updated successfully, but these errors were encountered:
Right, an artefact of our release workflow is that the commit that bumps the version and that highlights the breaking change isn't directly visible when the package gets released.
Now, to improve the changelog, we would need to have a changelog in the first place ;)
This provides a first level of schema validation for curated data extracts,
see #657 for context.
Goal is to make it easier to detect and document (through a changelog, so also
useful for #704) situations where we change the structure of data extracts.
Schemas, notably those that deal with parsed IDL structures, could go deeper
into details.
Tests are run against the curated version of data. That is not necessary for
extracts that aren't actually curated (dfns, headings, ids, links, refs), just
more convenient not to have branching logic in the test code.
we had two customers seeking clarity on the major bump of our latest @webref/css, which I take as a signal we should be more explicit about these :)
#688 (comment)
mdn/yari#6913 (comment)
The text was updated successfully, but these errors were encountered: