docs(contracts): apply compat-fallback taxonomy to resolved-layout fragmentIndex (SD-2923) - #3112
Conversation
…agmentIndex (SD-2923) The four `fragmentIndex` fields on ResolvedFragmentItem / Table / Image / Drawing previously used the word "legacy" with three different shades across the layout-engine - older path, current fallback, and removed code - all conflated. In this file, "legacy" actually means the *current load-bearing fallback* the painter uses to read inner content from Fragment until ResolvedFragmentItem carries full content directly. Apply the compat-fallback term from comment-policy.md uniformly: each fragmentIndex field now carries an AIDEV-NOTE: compat-fallback anchor naming what triggers the fallback (ResolvedFragmentItem missing content) and the retirement condition (paint items become self-describing). Drop "legacy content lookup" trailer from ResolvedFragmentItem.blockId and rewrite the type-level docstring to reference the per-field anchor instead of "legacy fragment renderers". This is the first in-the-wild use of the loaded-term taxonomy added in #3103. No behavior change.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
🎉 This PR is included in @superdoc-dev/mcp v0.3.0-next.38 The release is available on GitHub release |
|
🎉 This PR is included in @superdoc-dev/react v1.2.0-next.80 The release is available on GitHub release |
|
🎉 This PR is included in vscode-ext v2.3.0-next.82 |
|
🎉 This PR is included in superdoc v1.30.0-next.39 The release is available on GitHub release |
|
🎉 This PR is included in superdoc-cli v0.8.0-next.56 The release is available on GitHub release |
|
🎉 This PR is included in superdoc-sdk v1.8.0-next.41 |
|
🎉 This PR is included in superdoc-cli v0.9.0 The release is available on GitHub release |
|
🎉 This PR is included in superdoc v1.32.0 The release is available on GitHub release |
|
🎉 This PR is included in @superdoc-dev/mcp v0.4.0 The release is available on GitHub release |
|
🎉 This PR is included in @superdoc-dev/react v1.3.0 The release is available on GitHub release |
|
🎉 This PR is included in vscode-ext v2.4.0 |
|
🎉 This PR is included in superdoc-sdk v1.9.0 |
2 participants
First in-the-wild application of the loaded-term taxonomy added in #3103. The four
fragmentIndexfields onResolvedFragmentItem/Table/Image/Drawingpreviously used the word "legacy" with three different shades across thelayout-enginepackage: older path, current fallback, and removed code, all conflated. In this file, "legacy" actually meant the current load-bearing fallback the painter uses to read inner content fromFragmentuntilResolvedFragmentItemcarries full content directly.Apply the
compat-fallbackterm uniformly: eachfragmentIndexfield now carries anAIDEV-NOTE: compat-fallbackanchor naming what triggers the fallback (ResolvedFragmentItem missing content) and the retirement condition (paint items become self-describing). Drop the"and used for legacy content lookup"tail fromblockIdand rewrite the type-level docstring to point at the per-field anchor instead of "legacy fragment renderers".No behavior change. The point is to make the taxonomy a convention in code rather than just policy on paper.
Related: SD-2923 (comment hygiene umbrella).