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.

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

Standardize how LLM output is stored in a ProviderResponse output object #786

Open
efung opened this issue May 16, 2024 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@efung
Copy link
Contributor

efung commented May 16, 2024

ProviderResponse has an output field that is documented to be either a string or an object.

If it's a string, then the Web UI shows a nice diff between the LLM outputs when comparing two prompts or providers.

However, if it's an object, the serialized object is shown and you lose the nice diff output.

Can a convention be established about what goes into the object, specifically if a field with a specific key exists, then that represents the LLM output? (And any other fields can be visible in the Web UI if you click on the magnifying glass).

@typpo
Copy link
Collaborator

typpo commented May 17, 2024

This seems reasonable. What do you think we should call the displayed field? content, display, text?

@efung
Copy link
Contributor Author

efung commented May 17, 2024

This seems reasonable. What do you think we should call the displayed field? content, display, text?

I prefer text or content.

@typpo
Copy link
Collaborator

typpo commented Jun 7, 2024

Added a frontend configuration for this in #893

@typpo typpo added the enhancement New feature or request label Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants