Better type printing for JSX IntrinsicElements

Search Terms

JSX IntrinsicElements print

Suggestion

When printing JSX IntrinsicElements related types, prefer the tag name

Use Cases

Examples

const z1 = <a class="" />;

Now:

Type '{ class: string; }' is not assignable to type 'DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>'.

Suggest:

Type '{ class: string; }' is not assignable to type '<a />'.

This will make the error message easier to understand

Checklist

My suggestion meets these guidelines:

• 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, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

The issue names no files, tests, or entry points. Start by locating the compiler's JSX IntrinsicElements diagnostic and type-printing paths, then compare their output for the provided example. Done means the diagnostic uses the tag-name form while preserving the requested type-checking behavior.