fix: validate, limit, and escape merchant settings business data (#552) - #583
Open
Preciousuche wants to merge 1 commit into
Open
fix: validate, limit, and escape merchant settings business data (#552)#583Preciousuche wants to merge 1 commit into
Preciousuche wants to merge 1 commit into
Conversation
Contributor
|
kindly resolve conflict |
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
3 participants
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.
Adds length boundaries and validation constraints to the merchant settings business data fields inside Zod schemas (
businessName,supportEmail,supportAddress, andtier). Additionally, implements an HTML escaping filter for free-text fields to automatically sanitize inputs and neutralize potential XSS payloads. Integration and unit tests are included.Closes #552