Fix: Prevent 500 POST errors via strict frontend schema validation during Round Creation - #454
Closed
ayushshukla1807 wants to merge 1 commit into
Closed
Conversation
This was referenced Apr 1, 2026
Closed
Closed
Open
ayushshukla1807
force-pushed
the
gsoc-2026-ui-input-validation
branch
from
April 2, 2026 00:18
087b5f8 to
0a78447
Compare
This was referenced Apr 6, 2026
Contributor
Author
🧪 Local Testing VerificationI've successfully verified this fix locally. As shown in the screenshot below, when an organizer attempts to submit an empty form, the synchronous frontend validation intercepts the payload before the network request is fired. This immediately resolves the |
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.

Fixes #447.
Tightened the frontend constraints on
RoundNew.vueso people can't submit broken or empty round configurations and trigger unhandled 500 stack traces on the backend.