Add email badge endpoint#768
Conversation
- Add `pages/api/email.ts` to handle `/email/:tld/:name/:domain` - Register `/email` endpoint in `next.config.js` - Add E2E tests for the new email endpoint This implements the proposal from #293 (comment) Co-authored-by: amio <215282+amio@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
- Add `pages/api/email.ts` to handle `/email/:name/:domain` - Register `/email` endpoint in `next.config.js` - Add E2E tests for the new email endpoint in `test/email.test.mjs` This implements the email badge as requested, allowing users to provide the mailbox name and domain separately. Co-authored-by: amio <215282+amio@users.noreply.github.com>
|
also need to update |
I've updated |
- Add email badge endpoint with /email/:name/:domain schema - Register /email endpoint in next.config.js - Update libs/badge-list2.ts with email badge metadata - Add E2E tests for email badge Co-authored-by: amio <215282+amio@users.noreply.github.com>
I have added a new
/emailendpoint to generate email badges. The endpoint follows the pattern/email/<tld>/<name>/<domain>, which reconstructs the email address as<name>@<domain>.<tld>. This approach avoids putting the full email address in a single URL segment, helping to mitigate simple scrapers while still providing a functional badge.Key changes:
pages/api/email.tsusing the project's standardcreateBadgenHandler./emailprefix innext.config.jsto ensure it's correctly routed to the new API handler.test/email.test.mjsto verify the functionality.PR created automatically by Jules for task 5308397379689487379 started by @amio