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
docs(contracts): apply compat-fallback taxonomy to resolved-layout fragmentIndex (SD-2923) (#3112)
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.
0 commit comments