When using react-jsx, don't treat "key" property as special unless it's specified as IntrinsicAttribute about typescript HOT 6 CLOSED

It makes TSX more generic for use by any library, and less React specific

But... you specifically asked for react-jsx...

from typescript.

It makes TSX more generic for use by any library, and less React specific

But... you specifically asked for react-jsx...

If react-jsx is to be used only with react, then why don't we have "jsxImportSource" hardcoded to "react"? Or in other words, the ONLY way to use tsx for anything other than react is to set "jsx" to "preserve", because only "preserve" doesn't have the word react in it. Is that the official stance of TypeScript?

from typescript.

react-jsx means "compile JSX syntax using React semantics" so yes if your JSX flavor is non-React-compatible you would use preserve.

from typescript.

tsx for anything other than react

View frameworks exist that are not React, not React-compatible, but still are compatible only in the jsx function.

There's also the react preset for Typescript, which transforms to a function call (usually named React.createElement or h) with slightly different children semantics, and has no special semantics for key.

from typescript.

We don't do type-directed emit, which is what this is asking for.

jsx: react doesn't have the key special-casing; it's more accurately thought of as the JSX semantics of ~2016 that predate _jsx

jsx: react-jsx really does include React-specific semantics

jsx: preserve exists if neither of those work for your scenario

from typescript.

This issue has been marked as "Working as Intended" and has seen no recent activity. It has been automatically closed for house-keeping purposes.

from typescript.