Release playground v2 #247
Merged
Conversation
This file contains 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
Updates the main agents page with the V2 implementation featuring: - Enhanced card-based grid layout - Last updated timestamp display - Improved visual styling with gradients - Direct links to canary view Removes the separate agents-v2 route and consolidates the functionality into the main /agents path for a more streamlined experience.
Removes the playgroundV2 feature flag requirement from the canary view, making it accessible by default. This change indicates the canary version is now considered stable enough for general use. Note that the developer mode flag check is still maintained for restricted functionality.
Adds authorization check to ensure users can only access canary views for agents within their teams. This improves security by: - Verifying user team membership before showing agent data - Returning 404 for unauthorized access attempts - Handling both missing agents and insufficient permissions consistently The change enforces proper access control while maintaining a clean user experience by using notFound() instead of throwing errors.
Simplifies the playground routing by: - Removing playgroundV2 and view feature flags - Setting viewFlag permanently to true - Removing redirect to canary view - Hardcoding playgroundV2Flag to false for legacy components This cleanup indicates the V2/canary features are now part of the main user experience path rather than being feature-flagged.
Relocates the beta-proto implementation to a prev/ directory to clearly separate it as legacy code while maintaining backwards compatibility. Changes include: - Move beta-proto directory to prev/beta-proto - Update all import paths to reflect new location - Preserve functionality while better organizing codebase - Maintain existing database migrations and server actions This change prepares for the full transition to the new implementation while safely preserving the old one for reference and compatibility.
Moves canary implementation to be the primary playground experience by: - Moving all canary components/logic to main playground directory - Removing mock data files - Updating import paths across codebase - Preserving prev/ directory for legacy code This change completes the graduation of the canary features to production, making them the default experience while maintaining a clean directory structure.
|
@toyamarinyon is attempting to deploy a commit to the Edge Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@toyamarinyon Could you fix the deployment errors? |
shige
reviewed
Dec 17, 2024
app/(main)/agents/page.tsx
Outdated
| <CreateAgentButton createAgentAction={createAgentAction} /> | ||
| <div className="grid gap-[16px] grid-cols-3"> | ||
| {dbAgents.map((agent) => ( | ||
| <Link href={`/p/${agent.id}/canary`} key={agent.id}> |
There was a problem hiding this comment.
Suggested change
| <Link href={`/p/${agent.id}/canary`} key={agent.id}> | |
| <Link href={`/p/${agent.id}`} key={agent.id}> |
There was a problem hiding this comment.
@toyamarinyon I cannot open the agent page in /agents. Please check it and try your OAT.
## Changes
- Update agent card links to point to `/p/${agent.id}` instead of `/p/${agent.id}/canary`
- Remove deprecated canary path from navigation
|
@shige Sorry. I didn't check move to the playground of the agent clicked on the agent list page. I fix and check the following scenarios: Create agent
Move to the playground of the agent 🆕
Execute a node on the playground
Execute a flow on the playground
|
Co-authored-by: Tadashi Shigeoka <[email protected]>
3 tasks
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.
Note
This pull request will be conflict with #241.
Changes
Testing
Create agent
/agentsMove to the playground of the agent
/agentsExecute a node on the playground
/p/:agentIdExecute a flow on the playground
/p/:agentId