SWML TypeSpec @doc strings reach customers on two surfaces: the hand-written SWML reference MDX
restates them, and the REST reference embeds them, because the REST TypeSpec imports
specs/swml/calling at source level (see #584).
Bare fragment links like #paramsemotion or #languagesauto_emotion resolve only on the SWML
reference page whose ParamField path values generate those anchors. On the REST reference pages that
render the same models, they point at anchors that do not exist there.
Most of ai_languages.tsp already uses full /docs/... paths, so the bare-fragment form is the
minority pattern. Pre-existing; the #578 review fixes added two more instances while correcting a dead
anchor, following the file's local convention rather than widening the change.
Done when: spec @doc links use full paths, or the fragments are confirmed to resolve on every
surface that renders them.
SWML TypeSpec
@docstrings reach customers on two surfaces: the hand-written SWML reference MDXrestates them, and the REST reference embeds them, because the REST TypeSpec imports
specs/swml/callingat source level (see #584).Bare fragment links like
#paramsemotionor#languagesauto_emotionresolve only on the SWMLreference page whose
ParamField pathvalues generate those anchors. On the REST reference pages thatrender the same models, they point at anchors that do not exist there.
Most of
ai_languages.tspalready uses full/docs/...paths, so the bare-fragment form is theminority pattern. Pre-existing; the #578 review fixes added two more instances while correcting a dead
anchor, following the file's local convention rather than widening the change.
Done when: spec
@doclinks use full paths, or the fragments are confirmed to resolve on everysurface that renders them.