feat(events): publish and synchronize Discord forum posts (T-222) - #4
Draft
xfoxfu wants to merge 1 commit into
Draft
feat(events): publish and synchronize Discord forum posts (T-222)#4xfoxfu wants to merge 1 commit into
xfoxfu wants to merge 1 commit into
Conversation
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.
Event coordinators can publish a saved website event as a Discord forum post through
PUT /api/events/{id}/discord. Later event updates synchronize the existing title and starter message. A separateevent_discord_messagetable stores the association, text sync status, and last successful sync time; failed synchronization preserves website edits and supports retry.Discord publication runs in its own service after the event transaction commits. Apply the migration and configure
discord.event_forum_channel_id(and forum tags if required) before enabling publication. Concurrent first publications can create duplicate posts. The migration has not been exercised against a live database.Validation: rebased onto latest main; all 5 Discord tests passed using a local mock HTTP server;
git diff --checkpassed. No real Discord messages were sent.Tracks T-222.