Split out of #219 (investigate api dropping elements marked support=full), one element per issue.
What
<measure-numbering> is dropped on api round-trip, affecting ~88 corpus files. data/api.features.xml audits it as full.
To be determined (the point of this issue):
- a genuine impl round-trip bug - we model
measure-numbering but drop it on write (impl fix), or
api.features.xml overstating support - it is really partial/none and the audit is wrong (audit correction).
Repro
make dump-api-roundtrip && make classify-api-roundtrip
# build/api/classified.json: <measure-numbering> among the drop signatures
References
Split out of #219 (investigate api dropping elements marked support=full), one element per issue.
What
<measure-numbering>is dropped on api round-trip, affecting ~88 corpus files.data/api.features.xmlaudits it asfull.To be determined (the point of this issue):
measure-numberingbut drop it on write (impl fix), orapi.features.xmloverstating support - it is really partial/none and the audit is wrong (audit correction).Repro
References