add extra origin information for deprecation diagnostics#38052

Merged

DanielMSchmidt merged 11 commits intomainfrom

deprecation-diagnostics-extra-origin

Feb 3, 2026

Commits on Feb 3, 2026

add extra origin information for deprecation diagnostics
DanielMSchmidt
committed
refactor: extract write snippet in diagnostic rendering
DanielMSchmidt
committed
display origin of deprecated value in diagnostic
DanielMSchmidt
committed
contextualFromConfigBody should also apply for overridden diagnostics
DanielMSchmidt
committed
move stray check for deprecation to central location
DanielMSchmidt
committed
use a string as deprecation origin to help with indirect references
DanielMSchmidt
committed
deprecation.Validate should only check top-level marks
DanielMSchmidt
committed
we only want to send diagnostics for deeply nested deprecations in certain locations
DanielMSchmidt
committed
use validate for primitive types
DanielMSchmidt
committed
refactor into switch statement
DanielMSchmidt
committed
ElaborateFromConfigBody handles deeply nested paths more precisely
DanielMSchmidt
committed