Add all apostrophe types to api string validation #1019
Merged
Conversation
This file contains 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
Generated by E2E-Test |
georgimld
approved these changes
Nov 25, 2021
Stezido
force-pushed
the
adapt-api-joi-validation
branch
from
4dc0bfd
to
23363b9
Compare
Stezido
force-pushed
the
adapt-api-joi-validation
branch
from
23363b9
to
e749f83
Compare
Stezido
added
api
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.
Checklist
Description
The api's validation on normal fields are to restrictive. In some languages apostrophes are used quite often so they should be allowed in e.g. description fields. In Id or passwords fields they are still not allowed.