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.

L’issue ne mentionne aucun fichier, test ou point d’entrée. Commencez par localiser les chemins de diagnostic et d’affichage des types de JSX IntrinsicElements du compilateur, puis comparez leur sortie pour l’exemple fourni . Le travail est terminé lorsque le diagnostic utilise la forme du nom de balise tout en préservant le comportement de vérification de types demandé.