Product
Introducing License Enforcement in Socket
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
django-easy-validator
Advanced tools
this piece of software is inspired by the validation system of laravel, you can use this software to validate your POST/GET data easily and softly.
install from pypi :
pip install django-easy-validator
install from source code:
python setup.py install
from validator import Validator
class LoginValidator(Validator):
username = 'required|email'
password = 'required'
message = {
'username': {
'required': _('username is required'),
'email': _('username is not an email address')
},
'password': {
'required': _('password is required')
}
}
validator = LoginValidator({'username': 'michael', 'password': '12345678'})
status = validator.validate()
if status:
print("login succeed")
else:
errors = validator.get_message()
print(errors)
class LoginValidator(Validator):
username = 'required'
the field with required rule cant be null or empty.
class LoginValidator(Validator):
username = 'required'
remember_me = 'accepted'
the field with accepted must be one of the following strings, and the string case is insensitive.
['yes', 'no', 'true', 'false', '0', '1']
class RegisterValidator(Validator):
birthday = 'required|date:%Y-%m-%d'
the field with date must be a python date format string, the parameter should be a format suit the datetime.datetime.strptime function.
class SubmitValidator(Validator):
due = 'required|date_before:2017-12-31'
the field with date_before must be a date format string suit xxxx-mm-dd.
class SubmitValidator(Validator):
date = 'required|date_after:2017-11-12'
the field with date_after must be a date format string suit xxxx-mm-dd.
class SubmitValidator(Validator):
date_range = 'required|date_range:2017-01-01,2017-12-31'
the field with date_range must be 2 date format strings and it should suit xxxx-mm-dd.
class RegisterValidator(Validator):
login_time = 'required|datetime:%Y-%m-%d %H:%M:%S'
the field with datetime and the parameter must be a datetime string suit the datetime.datetime.strptime function.
class LoginValidator(Validator):
time = 'required|datetime_before:2017-12-12 13:14:00'
the field with datetime_before must be a datetime string can strap to a datetime object and so as the parameter.
class LoginValidator(Validator):
time = 'required|datetime_after:2017-12-12 13:14:00'
the field with datetime_after must be a datetime string can strap to a datetime object and so as the parameter.
class LoginValidator(Validator):
period = 'datetime_range:2017-12-12 13:14:00, 2017-12-15 13:14:00'
class ActiveURLValidator(Validator):
url = 'active_url'
the field with active_url must be a active url you could connect to and get reply.
class RegisterValidator(Validator):
id_number = 'required|numberic'
the field with numberic must be a number, it should be a integer not a float or something.
class RegisterValidator(Validator):
product_series = 'required|digits'
the field with digits must only contains digits token.
class RegisterValidator(Validator):
id_number = 'required|regex:^0[0-9]{5,10}$'
the field with regex must be a string, the parameter could be any regex pattern string, this rule will match the field value with the paramter pattern out.
class RegisterValidator(Validator):
username = 'required|email'
the field with email must be a valid email address string.
class Register(Validator):
password = 'min_length:8'
the field with min_length must has the minimal length of string or value of number.
class RegisterValidator(Validator):
username = 'max_length:20'
the field with min_length must has the minimal length of string or value of number.
class DeleteValidator(Validator):
ids = 'ids'
the field with ids must be a integer string splited by the comma, such as '1,2,3,4,5'
class RegisterValidator(Validator):
phone = 'cellphone'
the field with cellphone rule must be a real cellphone number , it could be '+8613811754531' or just '13811754531'
class RegisterValidator(Validator):
name = 'alphabet'
the field with alphabet must be a standard alphabet string.
class LoginValidator(Validator):
rememberme ='switch:yes,no'
the field with switch must be in the params array, it this case , rememberme must be yes or no.
class RegisterValidator(Validator):
username = 'unique:AUTH_USER_MODEL,username'
email = 'unique:account.User,email'
the field with unique must has 2 parameters , the first is appname.modelname, the second is the field to check, actually it is also the column to check if is already exists in this table, if you want to validate the django auth user, the first paramater must be AUTH_USER_MODEL.
class UpdateProfileValidator(Validator)
avatar = 'image|size:2048'
the field with size has 4 kind of types , if the given field is an file, the parameter means the size of the file with KB, if the field is a string , the parameter means the size is the string length, if the field is an integer , the size means the integer value, if the field is an array, the size means the array size.
class UpdateProfileValidator(Validator):
profile = 'image|min:2048'
the field with min has the same meaning of size, it's just check the minimal of the field , the size is check the equal of the field.
class UpdateProfileValidator(Validator):
profile = 'image|min:2048'
the field with min has the same meaning of size, it's just check the maximal of the field , the size is check the equal of the field.
class UploadValidator(Validator):
file = 'file:png,jpeg,zip,rar'
the field with file rule is to check the file type. parameters needed to be a string array.
class UploadValidator(Validator):
file = 'image'
the field with file image rule just do the same thing like file , it is a convenient way to check the common image type , in this way you do not need to add image ext parameter. the check type is ['png', 'jpeg', 'gif', 'jpg', 'svg'] .
class UploadValidator(Validator):
file = 'video'
the field with video rule just do the same thing like file , it is a convenient way to check the common video type , in this way you do not need to add video ext parameter. the check type is ['mp4', 'avi', 'mkv', 'flv', 'rmvb'].
class UploadValidator(Validator):
file = 'audio'
the field with audio rule just do the same thing like file , it is a convenient way to check the common audio type , in this way you do not need to add video ext parameter. the check type is ['mp3', 'wma', 'flac', 'ape', 'ogg'].
class UploadValidator(Validator):
file = 'attachement'
the field with attachement rule just do the same thing like file , it is a convenient way to check the common attachement type , in this way you do not need to add video ext parameter. the check type is ['doc', 'zip', 'ppt', 'docx', 'excel', 'rar'].
class RegisterValidator(Validator):
username = 'alpha_dash'
the field with alpha_dash rule is just check out if the string only includes alphabet characters and dash character.
class RegisterValidator(Validator):
username = 'alpha_number'
the field with alpha_number the given value must conbines with only alphabets and numbers.
class RegisterValidator(Validator):
hobbies = 'array'
the field with array must be a array string ,such as 'guitar, computer, music, food'.
class RegisterValidator(Validator):
due_at = 'date_before_equal:2018-01-08'
the field with date_before_equal just check the given value must be a date string and before or equal the given parameter.
class RegisterValidator(Validator):
due_at = 'date_after_equal:2018-01-08'
the field with date_after_equal just check the given value must be a date string and afer or equal the given parameter.
class RegisterValidator(Validator):
due_at='datetime_before_equal:1990-12-12 06:08:26'
the field with datetime_before_equal just check the given value must be a datetime string and befor the given parameter.
class RegisterValidator(Validator):
due_at='datetime_after_equal:1990-12-12 06:08:26'
the field with datetime_after_equal just check the given value must be a datetime string and after the given parameter.
class RegisterValidator(Validator):
age = 'between:10, 15'
the field with between requires the given field value must be a integer number and it's value must between the parameters.
class RegisterValidator(Valiadtor):
remember = 'boolean'
the field with boolean requires the given value should be one of this '['0', '1', 'true', 'false']'
class RegisterValidator(Validator):
username = 'username'
the field with username requires the given value starts with an alphabet character and it could includes with numbers , dash, underscore.
class RegisterValidator(Validator):
password = 'password:low'
the field with password ruls requires an parameter , it could be : low, middle , high. the 3 different check methods has different check level.
the low method means the password length must longer than 7
the middle method means the password length must longer than 7 and it sould contains lower , upper latin characters and digits
the high method means the password lenght must longer than 7 and it sould contains lower , upper latin characters and digits, and special
characters.
class ASCIIValidator(Validator):
ascii = 'ascii'
the ascii requires the given value only includes ascii characters.
class SameValidator(Validator):
password = 'required|min_lengh:8'
password_confirm = 'same:password'
the same rule just validate the give field vale checks the value if is same as the other value.
class DecimalValidator(Validator):
price = 'required|decimal'
the decimal rule just validate the give field value if is a decimal or a float number or number string.
class ExistValidator(Validator):
username = 'required|exist:AUTH_USER_MODEL,username'
the exist rule just check the given field record weather exists in the database table.
class UniqueAgainstValidator(Validator):
username = 'required|unique_against:AUTH_USER_MODEL, username, youngershen'
the unique_against validator check weather the given value column exists in the database and against the third parameter.
class PASCIIValidator(Validator):
username = 'required|pascii'
pascii ensure the input string must be a ascii string and it can't contians the unprintable ascii characters.
unblank make the given field must be a none-blank string, it could be empty, but if it is not empyt, it should be a unblank string.
the rule indicates the given field shoud be empty string or it should be a none-empty string, like '\r\n\r\n' it will return a False, becaus '\r\n' is A empty string, the '' wille return True, because it is a normal empty string.
this rule check the give value if it's a proper decimal integer
the positive value version the integer value
the negative value version the integer value
check the give value if it's a integer value from 0 to 100
just check the given value if it's a ip address, both checks for ip v4 and v6 address.
# define the rule
from validator import BaseRule
class TestRule(BaseRule):
name = 'test_rule'
message = 'test custom rule failed'
description = 'just for custom rule test'
def check_value(self):
self.status = True if self.field_value == 'test' else False
def check_null(self):
pass
# define a validator to use the rule
class TestRuleValidator(Validator):
name = 'test_rule'
# to run the validation
extra_rules = { TestRule.get_name(): TestRule }
validator = TestRuleValidator(extra_rules=extra_rules, data={'name': 'test'})
assert validator.validate()
custom a validation rule is very easy, you just import the BaseRule and implements the method , the most important thing is before you use your rule , you should pass it to your validator class when it init through the extra_rules parameter.
FAQs
a very easy use django request POST/GET data validator
We found that django-easy-validator demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
Product
We're launching a new set of license analysis and compliance features for analyzing, managing, and complying with licenses across a range of supported languages and ecosystems.
Product
We're excited to introduce Socket Optimize, a powerful CLI command to secure open source dependencies with tested, optimized package overrides.