You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is kindof annoying with all of the other stuff you have to do. Need to change it. We need some magic 🪄
There are a couple of ways we can do this.
I'm thinking that components in packages can have a special field added to them if they are a gradio component and we can autogenerate everything. Then the process of adding a new component to core will just be a case of adding a new package with this fields, respecting the documented structure and nothing else.
The alternative is adding a method (which we'll need for custom components anyway), something like register` would be magical but requires more work for devs and could introduce more tooling issues (typescript in particular).
This will need some TS declaration files either way I think.
The text was updated successfully, but these errors were encountered:
pngwn
changed the title
Remove the component directory hardcoding. There are a couple of ways we can do this. I'm thinking that components in packages can have a special field added to them and we can autogenerate everything. Then the process of adding a new component to core will just be a case of adding a new package and nothing else. Alternative is adding a method (which we'll need for custom components anyway), something like register` would be magical but requires more work for devs and could introduce more tooling issues (typescript in particular).
Make adding new components to core easier
Mar 2, 2023
Currently we register each component like this:
This is kindof annoying with all of the other stuff you have to do. Need to change it. We need some magic 🪄
There are a couple of ways we can do this.
I'm thinking that components in packages can have a special field added to them if they are a gradio component and we can autogenerate everything. Then the process of adding a new component to core will just be a case of adding a new package with this fields, respecting the documented structure and nothing else.
The alternative is adding a method (which we'll need for custom components anyway), something like register` would be magical but requires more work for devs and could introduce more tooling issues (typescript in particular).
This will need some TS declaration files either way I think.
The text was updated successfully, but these errors were encountered: