We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature/{ticket-id}-description
feature/5-regexp-type
#{ticket-id} :: {brief-description-of-the-change}
Example of valid commits
#5 :: Added new regexp type class #5 :: Refactor of main class in order to simplify strategy
Example of wrong commits
Update of class Update 5 > Change of logic
regexp[{expression}]
{expression}
i.e: We want to create a validation code as follow: ^[0-9]{1,6}$
^[0-9]{1,6}$
^ : Start anchor [0-9] : Character class to match one of the 10 digits {1,6} : Range quantifier. Minimum 1 repetition and maximum 6. $ : End anchor
Related filter
$filter = new Gcore\Sanitizer\Template\TemplateSanitizer([ 'email' => 'string', 'validation_code' => 'regexp[^[0-9]{1,6}$]', ]);
The text was updated successfully, but these errors were encountered:
#4 :: Add base class for regexp. Add to template [WIP]
33148d3
#4 :: Update readme for regexp type sanitizer
b6acb2f
ejaramillo
No branches or pull requests
Before you start
feature/{ticket-id}-description
. For this case will be:feature/5-regexp-type
#{ticket-id} :: {brief-description-of-the-change}
.Example of valid commits
Example of wrong commits
Tasks
regexp[{expression}]
where{expression}
will be the regular expression string.i.e: We want to create a validation code as follow:
^[0-9]{1,6}$
Related filter
The text was updated successfully, but these errors were encountered: