fix: use v2 templates in Sandbox Playground and quickstart - #26
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ca4b56e158
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| curl --fail --silent --show-error 'https://sandbox.sandbase.ai/v2/templates?limit=100' \ | ||
| -H "X-API-Key: $E2B_API_KEY" |
There was a problem hiding this comment.
When an organization has more than 100 templates, this command hides the X-Next-Token that the following paragraph requires, so users cannot discover or request later pages from the documented output. curl --help all documents --include as including response headers and --dump-header as writing them to a file, but neither option is present here; add one of them or provide a separate command that retrieves the pagination header.
Useful? React with 👍 / 👎.
1 participant
The Playground previously loaded
/v2/templatesand/templatestogether, so failure of the legacy endpoint blocked the template picker. It now uses only the paginated v2 response and enables templates whosebuildStatusisready. Names fall back throughnames,aliases, andtemplateID; non-ready builds remain visible with their status.Remove the legacy route from the docs proxy and update the SDK quickstart to use v2, including build status and pagination guidance. This follows merged PR #25.
Validation: 13 Playground tests passed, including multi-page v2 loading, unnamed templates, build readiness, and rejection of the legacy proxy route. Content, internal-link, public API surface checks and diff whitespace checks passed. A read-only production v2 request returned HTTP 200 with four templates (three public, one private), all with
buildStatus: ready. No sandbox was created or modified.