[OPIK-5161] [FE] Scope v2 Playground to active project#5927
[OPIK-5161] [FE] Scope v2 Playground to active project#5927
Conversation
Migrate the v2 Playground page from the hardcoded "playground" project to the active project context. Traces, rules, and metrics now use the project from the URL instead of a global "playground" project. - Pass active project name to trace/span creation (backward compatible) - Set source: "playground" on traces for proper source filtering - Scope rules and metrics queries to active project in RunOnDatasetDialog - Use activeProjectId for trace links and score containers - Remove project creation logic from RunOnDatasetDialog
|
🔄 Test environment deployment process has started Phase 1: Deploying base version You can monitor the progress here. |
apps/opik-frontend/src/v2/pages/PlaygroundPage/useActionButtonActions.tsx
Show resolved
Hide resolved
|
✅ Test environment is now available! To configure additional Environment variables for your environment, run [Deploy Opik AdHoc Environment workflow] (https://github.com/comet-ml/comet-deployment/actions/workflows/deploy_opik_adhoc_env.yaml) Access Information
The deployment has completed successfully and the version has been verified. |
|
🌙 Nightly cleanup: The test environment for this PR ( |
|
🌙 Nightly cleanup: The test environment for this PR ( |
Details
Migrates the v2 Playground page from the hardcoded "playground" project to the active project context from the URL. This is part of the IA revamp (OPIK-4617) to make all pages project-scoped in v2.
Key changes:
PLAYGROUND_PROJECT_NAMEconstantsource: "playground"on traces for proper source-based filtering (R3)RunOnDatasetDialogscoped to the active project viauseActiveProjectId()activeProjectIdinstead of looking up the "playground" project by nameRunOnDatasetDialog(no longer needed — active project always exists in v2)createLogPlaygroundProcessorare backward compatible (newprojectNameparam defaults toPLAYGROUND_PROJECT_NAME)Not included (deferred):
TraceLogsSidebarintegration (depends on T6) — playground traces are accessible by clicking individual output cells but not listed on the Logs page (by design, Logs filterssource = sdk)Change checklist
Issues
Testing
Documentation
N/A