feat: newsletter flows and admin-only e2e coverage (#1400, #1401, #1402, #1403) - #1430
Open
Fidelis900 wants to merge 4 commits into
Open
feat: newsletter flows and admin-only e2e coverage (#1400, #1401, #1402, #1403)#1430Fidelis900 wants to merge 4 commits into
Fidelis900 wants to merge 4 commits into
Conversation
|
@Fidelis900 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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
This PR addresses and implements the requirements for issues #1400, #1401, #1402, and #1403 across the newsletter and admin dashboard areas.
Detailed Changes
1. #1400 [Admin Dashboard] Add e2e coverage for admin-only flows
frontend/e2e/admin.spec.tsPOST /api/v1/admin/api-keys/rotate,GET /api/v1/admin/api-keys), verifying that rotated keys become active and functional.GET /api/v1/audit/logs,GET /api/v1/audit/statistics) covering pagination and action/resource-type filtering.GET /api/v1/email/queue/stats,GET /api/v1/email/queue/dead-letter,POST /api/v1/email/queue/dead-letter/:job_id/requeue).401 Unauthorizedfor unauthenticated or invalid API key requests.ADMIN_API_KEYis not configured in the environment.2. #1401 [Newsletter] Build newsletter signup form
frontend/src/components/NewsletterSignup.tsxNewsletterSignupcomponent handling double opt-in newsletter subscriptions.POST /api/v1/newsletter/subscribe.3. #1402 [Newsletter] Build unsubscribe page
frontend/src/app/newsletter/unsubscribe/page.tsxtokenoremailparameters are present in URL search params, with fallback to manual confirmation.4. #1403 [Newsletter] Build GDPR data-export request page
frontend/src/app/account/privacy/export/page.tsx,frontend/src/lib/api/public-client.tsPOST /api/v1/newsletter/gdpr/request-token; Step 2: Submit export request viaPOST /api/v1/newsletter/gdpr/export).newsletterGdprRequestTokenand updatednewsletterGdprExportinpublic-client.tsto support passing token payloads in the request body.POSTJSON request bodies and component state, ensuring no email addresses leak into URLs, browser history, or server access logs.predictiq-gdpr-data-export.json).Linked Issues
Closes #1400
Closes #1401
Closes #1402
Closes #1403