We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We currently use React 18 in our example, and also to define the JSX interface.
declare global { // eslint-disable-next-line @typescript-eslint/no-namespace namespace JSX { interface IntrinsicElements { 'gs-location-filter': DetailedHTMLProps<HTMLAttributes<HTMLElement>, HTMLElement>; } } }
The syntax now changed: https://react.dev/blog/2024/04/25/react-19-upgrade-guide#the-jsx-namespace-in-typescript
Now one should use
declare module "react" { namespace JSX { interface IntrinsicElements { "my-element": { myElementProps: string; }; } } }
Investigate, If we can use the new syntax, while still being able to use the components in react 18.
The text was updated successfully, but these errors were encountered:
fengelniederhammer
Successfully merging a pull request may close this issue.
We currently use React 18 in our example, and also to define the JSX interface.
The syntax now changed: https://react.dev/blog/2024/04/25/react-19-upgrade-guide#the-jsx-namespace-in-typescript
Now one should use
Investigate, If we can use the new syntax, while still being able to use the components in react 18.
The text was updated successfully, but these errors were encountered: