You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(frontend): preview seven new /m developer views - #8107
This moves seven tested /m developer views from hidden to preview. In preview, a view has a switch in Settings > Preferences > Feature Flags. Only a user who turns the switch on sees the view, under "Developer" in the /m navigation. Everyone else sees no change.
How a user turns a view on: open Settings > Preferences, find the view's name under Feature Flags, and switch it on. The setting is stored per user.
The seven views:
Archived apps: lists archived apps and lets the user restore one.
Annotation queues: lists annotation queues and opens one to review its items. It also lets the user add traces to a queue.
Evaluators: lists automatic and human evaluators, with archive and restore.
Variants: shows an app's variants and revisions, and where each is deployed.
Endpoints: shows the code to call an app and fetch its config, per environment.
Prompts: shows the prompts page under Developer.
Filter by app (feature gate on traces and sessions): adds an app filter to traces and lets a link open the sessions of one agent.
Changes:
developerViews.ts: seven stage values go from hidden to preview. The Archived apps switch text was a fragment ("Archived apps, with Restore."). It now says "Show the Archived apps page under Developer in the navigation. Restore an app from it."
Tests that pinned the old stages now pin preview. The Preferences structure test lists the seven switches.
New developerViewStages.test.ts lists exactly which views are in preview, which are hidden, and that none is on. A later stage change then shows in review.
Every preview view with routes has a first route without params and a nav entry. The route pages already sit behind DeveloperViewGate. The app filter has no route. Its screens read the same flag, and the existing render tests cover it.
Checks (run on the second machine): types, lint (0 errors), full mobile tests (311 files, 2205 tests), and speed:check (size budget passes; app shell 882.3 KB gzip, under its limit). The change adds one short text string and no code, so the shell does not grow beyond 0.1 KB.
Not checked: no screenshot was taken of Preferences.
No actionable comments were generated in the recent review.
Summary
Summary by CodeRabbit
New Features
Archived apps, Endpoints, Filter by app, Annotation queues, Variants, Prompts, and Evaluators are now available as preview options in Preferences.
Preview views remain opt-in; their routes stay unavailable until enabled.
The Archived apps description now explains where to find it and how to restore apps.
Seven developer views change from the hidden stage to preview. Unit tests verify stage assignments, preview navigation metadata, route expectations, and the developer-view rows shown in mobile Preferences.
Changes: Developer view preview stages
Layer / File(s)
Summary
Registry stages and preview metadata web/mobile/src/features/developer/developerViews.ts, web/mobile/tests/unit/developerViewStages.test.ts
Seven developer-view entries now use the preview stage. The archived-apps description specifies its Developer navigation placement and restore action. Tests check stage membership and preview navigation metadata.
Route and Preferences expectations web/mobile/tests/unit/archivedAppsScreen.render.test.tsx, web/mobile/tests/unit/developerViews.registry.test.tsx, web/mobile/tests/unit/developerViews.render.test.tsx, web/mobile/tests/unit/observabilityAppFilterRegistry.test.ts, web/mobile/tests/unit/preferencesTab.render.test.tsx, web/mobile/tests/unit/variantsRoute.render.test.tsx
Tests expect preview stages for the affected views. The Preferences test expects eight developer-view rows under Feature Flags.
Seven developer views become opt-in previews. The Prompts preview lets users browse and manage prompts but not open their contents. This affects only users who enable it, so the risk is bounded, and the PR itself says not to merge until the product decision is made.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly and concisely describes moving seven frontend developer views to preview, matching the main changeset.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description check
The description states the PR moves seven tested /m developer views from hidden to preview, explains how users enable each view under Settings > Preferences > Feature Flags, lists each view, and summa…
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 8 files.
Full details: Description check
Explanation
The description states the PR moves seven tested /m developer views from hidden to preview, explains how users enable each view under Settings > Preferences > Feature Flags, lists each view, and summarizes the test and check results. It matches the changeset in developerViews.ts, the updated tests, and the Archived apps switch text change, so it is related and specific.
Finishing Touches
Generate docstrings
Commit to this branch
Create a new PR
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 5 remain after this review.
Dependent tests finished. Post /preview for manual review. Environment absence verified; retained storage requires separate provider accounting.
Post /preview as a new comment to request a one-hour preview. Repeating it while active does not extend the hour.
Preview data is disposable. Expiry is enforced by the next successful cleanup sweep, not an exact timer.
Environment deletion stops its compute. Provider-retained storage and permanent services may still be billed.
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
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.
This moves seven tested /m developer views from hidden to preview. In preview, a view has a switch in Settings > Preferences > Feature Flags. Only a user who turns the switch on sees the view, under "Developer" in the /m navigation. Everyone else sees no change.
How a user turns a view on: open Settings > Preferences, find the view's name under Feature Flags, and switch it on. The setting is stored per user.
The seven views:
Changes:
developerViews.ts: sevenstagevalues go fromhiddentopreview. The Archived apps switch text was a fragment ("Archived apps, with Restore."). It now says "Show the Archived apps page under Developer in the navigation. Restore an app from it."preview. The Preferences structure test lists the seven switches.developerViewStages.test.tslists exactly which views are in preview, which are hidden, and that none is on. A later stage change then shows in review.DeveloperViewGate. The app filter has no route. Its screens read the same flag, and the existing render tests cover it.Checks (run on the second machine): types, lint (0 errors), full mobile tests (311 files, 2205 tests), and
speed:check(size budget passes; app shell 882.3 KB gzip, under its limit). The change adds one short text string and no code, so the shell does not grow beyond 0.1 KB.Not checked: no screenshot was taken of Preferences.