Skip to content
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.

Sign up for GitHub

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

Jump to bottom

'use via API' page should (could?) use live values #8501

Open
1 task done
pngwn opened this issue Jun 7, 2024 · 1 comment
Open
1 task done

'use via API' page should (could?) use live values #8501

pngwn opened this issue Jun 7, 2024 · 1 comment
Labels
gradio_client Related to the one of the gradio client libraries needs designing The proposed feature needs to be discussed and designed before being implemented

Comments

@pngwn
Copy link
Member

pngwn commented Jun 7, 2024

  • I have searched to see if a similar issue already exists.

One of my favourite things about gradio app + API. Is playing around with various parameters and finding something that works well before committing that and using it via the API. However, the API snippet doesn't reflect the live values from the app itself.

We have all of the information in order to do this, and I think it would be nice for two reasons:

  • the above workflow
  • the default values ion the API page often don't work well, the default values for the components are often much better. If we use live values then we'd get these for free.
@pngwn pngwn added needs designing The proposed feature needs to be discussed and designed before being implemented gradio_client Related to the one of the gradio client libraries labels Jun 7, 2024
@abidlabs
Copy link
Member

abidlabs commented Jun 8, 2024

+1
@pngwn pngwn self-assigned this Jun 9, 2024
@pngwn pngwn removed their assignment Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gradio_client Related to the one of the gradio client libraries needs designing The proposed feature needs to be discussed and designed before being implemented
2 participants
@abidlabs @pngwn