Update Gradio description to clarify text-based input #427
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
February 28, 2023 15:08
|
The documentation is not available anymore as the PR was closed or merged. |
lvwerra
approved these changes
Mar 14, 2023
unna97
pushed a commit
to unna97/evaluate
that referenced
this pull request
Mar 20, 2023
* update Gradio description * make style
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on internal Slack.
The input format for text-based metrics is not always clear. The Gradio app requires JSON-like input (so text enclosed in double quotes). If that is not given, an error is raised but not error details are given.
While ultimately a more informative error message would be the better solution, this PR provides a temporary solution by simply telling users the expected input format for text-based metrics.