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
Close the last raw-stderr default in the plugin diagnostics chain
resolvePluginWarningHandler still fell back to a raw stderr write when
given neither a diagnostics collector nor an explicit onWarning, the
same silent-default shape that produced four rounds of one-off fixes
at the call-site level. Make the choice a required discriminated
union (diagnostics or onWarning, no third option) so the compiler
enumerates every caller.
pluginWarningSink drops its own fallback parameter, since that was
only ever reachable through the branch just removed.
Each of the five call sites the compiler surfaced now builds its own
explicit union locally: real callers that hold a diagnostics
collector keep using it, and the handful of standalone/test call
sites that pass neither get a raw stderr writer chosen visibly in
that function's own body, not inherited from a shared library
default.
Extends the behavioural stderr-capture test to pin that
resolveToolPlugins still falls back correctly (one write per
warning) when called with no collector at all.
0 commit comments