[x] I have searched to see if a similar issue already exists.
Is your feature request related to a problem? Please describe.
The new share button is amazing, however with the "Share to community" button we used to hand-craft, depending on the type of the demo, it kind of required context of what the input was. So the shared item was a combination of inputs / outputs (be it the prompt, or an image in case of image2image demos). The native share button only shares the output. This is limiting.
For example, for the image editing demo, you may want to include what was the source image before editing, and maybe the prompt too:
Describe the solution you'd like
Some suggestions:
Either a field like share_inputs that you can pass which input fields would also have its values shared
Or something like a .share() API on the component (e.g.: gradio.Image.share()) where you could craft the default message generated in the community, incl. all fields.
Also enable this sharing with the right inputs and outputs to be made on a dedicated button
Is your feature request related to a problem? Please describe.
The new share button is amazing, however with the "Share to community" button we used to hand-craft, depending on the type of the demo, it kind of required context of what the input was. So the shared item was a combination of inputs / outputs (be it the prompt, or an image in case of image2image demos). The native share button only shares the output. This is limiting.
For example, for the image editing demo, you may want to include what was the source image before editing, and maybe the prompt too:
Describe the solution you'd like
Some suggestions:
share_inputs
that you can pass which input fields would also have its values shared.share()
API on the component (e.g.:gradio.Image.share()
) where you could craft the default message generated in the community, incl. all fields.