Allowempty permits non-map values about pykwalify HOT 2 CLOSED

@kesre This fix for this was commited in this commit 8fa18e3 and it fixed the problem. The correct way to deal with this was to move the type checking earlier in the mapping validation so that even if you do not speciefy the mapping keyword and the value type is wrong you should get a error that the value type is bad.

Just to clearify that the keyword allowempty have no impact on this. You really need to have the correct value type before it will be applied or even considered. The correct solution was to give a type error first.

Please open a new issue if you find any other issues with the keyword allowempty

from pykwalify.

Not very familiar with the code at all, but at a brief glance,

I'm wondering if this happens because _validate_mapping returns too eagerly in the case of allowempty. (

I'd expect some sort of check that the value is a mapping at all by the time it gets to _validate_mapping.

from pykwalify.