Add "definedIn" property to dfns extract #446
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
definedIn
property captures the context under which the definition appears in the specification. Value may be one of:<dt>
<pre>
<table>
<h1>
,<h2>
,<h3>
,<h4>
,<h5>
,<h6>
note
classexample
classThis information is meant to be used for analysis purpose, e.g. to identify cases where a definition used by a spec is incorrectly defined in a Note, or where an IDL definition appears in an IDL block instead of in the prose of the specification.
Other projects may also perhaps use that information, likely in combination with
type
, to assess whether they should link to the definition itself or to the section that contains the definition. See related discussion in mdn/browser-compat-data#6765 (comment)The classification may evolve based on feedback.