Allow content mappers emit diagnostics with different severity levels #64932

🔍 Search Terms

content mappers, diagnostics, warning

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Currently, all diagnostics returned by a content mappers are treated as errors. It would be nice if content mappers could also produce warnings

📃 Motivating Example

For example, a Svelte content mapper could emit warnings for the svelte's compiler warnings.

💻 Use Cases

Use cases are clear, I think. All diagnostics being treated as errors is incorrect, and having warnings is very useful.