-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
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
StepperPanel: New const instead of class components are no valid JSX.Element's #6334
StepperPanel: New const instead of class components are no valid JSX.Element's #6334
Comments
I think i fixed it with this: #6325 |
Hi, With release 10.6.3 the issue should be fixed. If you notice that the issue persists, please ping me. |
@gucal I've updated the stackblitz: https://stackblitz.com/edit/vitejs-vite-9mym3z?file=src%2FApp.tsx |
What about the following type definition? That works locally for me and should be a proper type. |
@dvpritzbuer do you want to submit a PR by any chance? |
@melloware yes, I can do that |
OK i assigned to you! |
@melloware |
Yeah on GitHub you can only create PR's from a fork: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request |
* fix: typescript definition for Stepper and StepperPanel components * added type StepperRefAttributes for proper ref methods type definition of Stepper * added type StepperRefAttributes for proper ref methods type definition of Stepper
Describe the bug
"JSX element type 'Stepper' does not have any construct or call signatures."
"ERROR(TypeScript) 'StepperPanel' cannot be used as a JSX component.
Its type 'Component<StepperPanelProps, any, any>' is not a valid JSX element type."
Reproducer
https://stackblitz.com/edit/vitejs-vite-9mym3z?file=src%2FApp.tsx,package.json
PrimeReact version
10.6.2
React version
18.x
Language
TypeScript
Build / Runtime
Vite
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: