Skip to content

RM-251: User & Guild Exports - #131

Open
BenHall-1 wants to merge 3 commits into
masterfrom
RM-251
Open

BenHall-1 wants to merge 3 commits into
masterfrom
RM-251

Conversation

@BenHall-1

@BenHall-1 BenHall-1 commented Mar 26, 2026 •

Copy link
Copy Markdown
Member

Signed-off-by: Ben <ben@tickets.bot>
Refactors GDPR confirm button handling into a shared execution path, reducing duplicated queue/log/publish logic across all GDPR request types. Confirmation payloads are now stored in Redis behind short one-time tokens, so custom IDs stay within Discord limits and replay/double-clicks are prevented by consume-once semantics.

The GDPR modals now generate token-based confirm IDs, adds a new `gdpr.error.confirmation_expired` message key for expired/used confirmations, removes legacy custom-id guild parsing, and tightens transcript ownership checks to closed tickets only (`open = false`). Also updates GDPR export UI behavior/details (select placeholder and export-user confirmation reply flow).
Add a shared guild validation helper that fetches guilds via Discord REST instead of cache to avoid stale ownership/access data. GDPR transcript/export handlers now block requests when any target guild is unreachable, return a dedicated `gdpr.error.bot_not_in_server` error with guild references, and reuse the validated guild names/IDs for confirmations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants