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
DOCPCache referenced via @ref in two docstrings, but has no docstring of its own #630
Both direct_shooting.jl:119 and collocation.jl:115 document their return value as "...holding a DOCPCache with the precomputed DOCP." DOCPCache has no docstring anywhere in the repository, so the @ref can never resolve.
Surfaced while diagnosing OptimalControl's docs/make.jlwarnonly backlog (control-toolbox/OptimalControl.jl, Phase D of the documentation campaign): both instances fire as Cannot resolve @ref for md"[\DOCPCache`](@ref)"on OptimalControl's generatedapi/solving.md, since direct_shooting/collocation`-backed functions are re-exported there.
The source: direct_shooting.jl:119 and collocation.jl:115 (well, CTSolvers.discretize's two per-strategy docstrings) now write plain `DOCPCache` instead of [`DOCPCache`](@ref).
The consumer build: rebuilt OptimalControl's docs against 1.1.4-beta — the two Cannot resolve @ref for md"[DOCPCache](@ref)" warnings on api/solving.md are gone (0/0, down from 2).
Activity
ocots commentedon Aug 30, 2026
Verified in 1.1.4-beta — confirmed both ways:
direct_shooting.jl:119andcollocation.jl:115(well,CTSolvers.discretize's two per-strategy docstrings) now write plain`DOCPCache`instead of[`DOCPCache`](@ref).Cannot resolve @ref for md"[DOCPCache](@ref)"warnings onapi/solving.mdare gone (0/0, down from 2).Closing.
🤖 Generated with Claude Code