Skip to content

Create GraphQL Playground #377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kenkenseb wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

Create GraphQL Playground #377

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
05eb0ca
Create GraphQL Playground
kenkenseb Jul 29, 2026
88f421a
Update GraphQL Playground
kenkenseb Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions GraphQL Playground
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
https://www.figma.com/design/OhOGPhmbRZM9rlYWENffXf/Untitled?node-id=4-2&t=6QHWhg5S5r2LDtuV-1

@Depo-dev Depo-dev Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same situation as #376: this adds one file containing a single Figma URL, with no code.

The description goes further than #376 in describing implementation that isn't here — it specifies embed.FS serving with zero external dependencies, a PLAYGROUND_ENABLED=false gate, a pre-populated X-API-Key header, and a production fallback for when introspection is disabled. Those are real backend behaviours with security implications (introspection gating in particular), and none of them are implemented in this diff.

Problems:

  1. Closes #68 would auto-close an unimplemented feature. Issue feat(go-api): GraphQL Playground at /playground #68 (feat(go-api): GraphQL Playground at /playground) is open and unbuilt. Merging this closes it while delivering no endpoint.

  2. Filename GraphQL Playground — space, no extension. Same tooling/globbing problem as Create developer dashboard — event browser UI #376.

  3. The security-relevant parts need actual code review. Introspection gating and API key handling are exactly the things that need to be reviewed as code, not as a mockup.

Please close this and move the Figma link to a comment on #68, leaving the issue open. If you want to implement it, a fresh PR with the /playground handler, the PLAYGROUND_ENABLED gate, and tests for the disabled-in-production path would be very welcome — the design gives a clear target to build against.