feat: 'Report a problem' button with Slack webhook - #43
Merged
Conversation
- API route POST /api/report forwards to SLACK_REPORT_WEBHOOK_URL - Webhook URL stays server-side (env var, never client-bundled) - Discreet trigger placed next to 'Source code' on bench detail - Modal: textarea (5-2000 chars) + optional contact field - Slack payload includes bench slug, chain, page URL, contact, IP, UA
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Report a problembutton at the bottom of each bench detail page (next to theSource codelink)POST /api/reportroute that forwards to a Slack webhookSLACK_REPORT_WEBHOOK_URLenv var — never reaches the clientSetup
SLACK_REPORT_WEBHOOK_URLmust be set in Vercel (already configured for production)Test plan
Report a problem