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
Allow content mappers emit diagnostics with different severity levelsΒ #64932
Warnings kinda do exists in tsc though, the compiler just never produces them. There is diagnostic.category and it's properly handled by the cli and lsp. The pipeline sometimes assumes that all diagnostics are errors, but that's an easy fix.
Adding this will add the new semantics of "errors fail the build, warnings don't" which is not a concept that existed before, but I think it's the most normal thing ever.
Also, it might be a little weird that the compiler itself never produces warnings but content mappers can. Although the weird part is really that the typescript compiler doesn't have warnings.
Activity
RyanCavanaugh commentedon Oct 26, 2026
Notably, TS itself does not have a 'warning' concept, so this is a heavy lift on its own
blt-r commentedon Oct 26, 2026
Warnings kinda do exists in
tscthough, the compiler just never produces them. There isdiagnostic.categoryand it's properly handled by the cli and lsp. The pipeline sometimes assumes that all diagnostics are errors, but that's an easy fix.Adding this will add the new semantics of "errors fail the build, warnings don't" which is not a concept that existed before, but I think it's the most normal thing ever.
Also, it might be a little weird that the compiler itself never produces warnings but content mappers can. Although the weird part is really that the typescript compiler doesn't have warnings.
I can make a PR, this is a small change