-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
custom component templating not working for some components #5952
Comments
Does this work with 'Model3D'? |
No, that was the first thing I tried since that is the classname of the gradio component. Since it looks for the folder
|
Thanks for filing @duerrsimon ! Templating Model3D works on the ![]() |
Since this is working now, closing this issue. |
Describe the bug
The following command doesn't work:
gradio_component create Model3dTest --template model3d --install --overwrite
The folder for model3D does exist but I guess there is some automatic conversion to lowercase going on. If I rename
miniconda3/envs/gradio_customcomponents/lib/python3.9/site-packages/gradio/_frontend_code/model3D/
tomodel3d
the error messages changes fromFileNotFoundError: [Errno 2] No such file or directory:
toValueError: Cannot find model3d in gradio.components or gradio.layouts. Please pass in a valid component name via the --template option. It must match the name of the python class exactly.
Have you searched existing issues? 🔎
Reproduction
run command above
Screenshot
No response
Logs
No response
System Info
Severity
Blocking usage of gradio
The text was updated successfully, but these errors were encountered: