length constraint passes for empty string about pykwalify HOT 2 CLOSED

In my world the order the rules would apply would be.

• required, because that would apply to the key existing
• type, and this is the error that should be raised in your case because None != str type
• any other scalar checks

The issue from a quick look at the problem is that '_validate_scalar()' is not runned on the value for some reason. I will look it up closer later tonight.

from pykwalify.

Problem fixed with db5f7f0 Your schema now raises the following error.

ERROR - ["Value: None is not of type 'str' : /streams/0/name"]
Traceback (most recent call last):
  File "scripts/pykwalify", line 22, in <module>
    pykwalify.cli.main()
  File "/home/grok/code/pykwalify/pykwalify/cli.py", line 96, in main
    c.validate()
  File "/home/grok/code/pykwalify/pykwalify/core.py", line 92, in validate
    raise SchemaError("validation.invalid : {}".format(errors))
pykwalify.errors.SchemaError: <SchemaError: error code 6: validation.invalid : ["Value: None is not of type 'str' : /streams/0/name"]>

The problem was that when validating scalar type it would check if value is None and just return out of that function silent and the typechecking was done last in the check function and because of that it was not used in your case. Now the typechecking is done first so type errors is detected.

I will add your schema as a test in later commit and add one fix to scalar type checking so that you can specify None as a type.

from pykwalify.