Playground: add video generation support and refactor token context setup - #3
Merged
Merged
Conversation
This file contains hidden or 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
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.
Motivation
Description
setupPlaygroundTokenContextto centralize writing user context and temporary token setup and updatePlaygroundto use it viaRelay.PlaygroundVideoSubmitandPlaygroundVideoFetchhandlers and register new routesPOST /pg/video/generationsandGET /pg/video/generations/:task_idin the router.GeneralOpenAIRequestwithsecondsandqualityfields to support video generation parameters.SettingsPanel(size,seconds,quality), add constants and defaults inplayground.constants.js, and wire those fields into payload construction inhelpers/api.jswhere video requests force non-streaming and setsize,seconds, andquality.useApiRequesthook to detect video payloads, build a simplified video request payload from the last user message (extracting text and image), route requests toAPI_ENDPOINTS.VIDEO_GENERATIONS, handle non-stream responses for video tasks by summarizing task info into the message, and ensure streaming logic respects endpoints that must be non-streaming.Testing
go test ./...which completed successfully.yarn buildand ran type checks/linting, which succeeded./pg/video/generationssubmit and fetch flows which returned expected task summaries in the Playground UI.Codex Task