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
{{ message }}
Repository navigation
Commit db91010
Browse filesBrowse the repository at this point in the historyBrowse files
fix(docs-infra): stop generating member anchors that do not exist
When `{@link Foo}` does not resolve, the renderer falls back to
`CurrentSymbol.Foo` without checking that `Foo` is a member of the symbol being
rendered, so it emits a URL to an anchor that does not exist. `DefaultExport` is
rendered in both core and router while `injectAsync` is only in core's entries,
so /api/router/DefaultExport links `injectAsync` to
/api/router/DefaultExport#injectAsync.
Resolve the symbol first, and only fall back to the member form when the symbol
really is a member. A property on a function entry, and an initializer API
function, no longer take a fragment at all. Make the `@see` on `DefaultExport`
an absolute link so it resolves from every package that renders it.
Two consequences worth calling out. A `{@link}` that resolves to nothing now
fails the docs build where it used to emit a broken anchor, including a
core-only symbol referenced from a type another package re-exports. And an
explicit `{@link}` no longer consults the auto-linking exemption list, which is
what lets `{@link Event}` on `RouterEvent` reach /api/router/Event instead of a
fragment on itself.
(cherry picked from commit c863e00)
0 commit comments