fix: trim contact form values before sending to backend - #1007
Open
tylrx404 wants to merge 1 commit into
Open
Conversation
Contributor
|
@tylrx404 is attempting to deploy a commit to the Shivayan's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
Description
Closes #1001
Summary
This PR ensures that the contact form submits trimmed values instead of the raw user input.
Changes Made
trimmedFormDataobject before making the API request.nameemailsubjectmessageWhy
Previously, the form validated trimmed values but submitted the original untrimmed values to the backend, allowing leading and trailing whitespace to be sent in the request payload.
Validation
git diff --checkpasses successfully.npm run lintsuccessfully (no new lint errors introduced; only pre-existing warnings remain).