Fix: return and display community submission confirmation ID (closes #66)#68
Merged
Conversation
Signed-off-by: sethwebster <sethwebster@gmail.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
@sethwebster All CI checks are green on this automation-authored PR, but branch policy still requires a separate approval before merge. This is scoped just to returning + displaying the community submission confirmation ID for #66, with regression tests in place. |
sethwebster
approved these changes
May 15, 2026
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
POST /api/communities/submitRoot Cause
The submission flow already generated a unique
submission-*ID server-side, but the API dropped it from the success response and the client had no way to surface it. Users could see a success message without retaining any durable reference for later follow-up.Solution
submissionIdin the successful route responseTest Plan
npx tsc --noEmitValidation
npx vitest run src/app/api/communities/submit/route.test.ts src/components/communities/AddCommunityForm.test.tsx --project unit --silentnpx vitest run --project unit --silentnpx tsc --noEmitnpm run lint -- --max-warnings=0 src/app/api/communities/submit/route.ts src/components/communities/AddCommunityForm.tsx src/app/api/communities/submit/route.test.ts src/components/communities/AddCommunityForm.test.tsx