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

feat(ui) - swap OpenAI API with LF API #528

Closed
andrewrisse opened this issue May 16, 2024 · 0 comments · Fixed by #553
Closed

feat(ui) - swap OpenAI API with LF API #528

andrewrisse opened this issue May 16, 2024 · 0 comments · Fixed by #553
Assignees
Labels
enhancement ✨ New feature or request

Comments

@andrewrisse
Copy link
Contributor

User Story

As a frontend developer
I want to use the OpenAI API instead of Leapfrog API
So that I can build new features for the UI before the backend capacility is ready. I want to use real OpenAI so that we can also test Leapfrog API's conformity with the OpenAI spec.

Acceptance Criteria

Given I change my environment variables for the frontend application
When I use the app
Then I am getting responses from OpenAI and I can use assistants with OpenAI

Describe alternatives you've considered

We could just mock these endpoints, but if we use real OpenAI, we can also test Leapfrog API's conformity with the OpenAI spec.

Additional context

Will need to update naming conventions to use threads instead of conversations. Also try to use more types from Vercel AI SDK instead of our own types.

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

Successfully merging a pull request may close this issue.

1 participant