The practice of accepting None as a valid value for optional keys is surprising and hard to debug. I don't feel it should be accepted in a schema managed file, particularly if the strict mode is specified. Possibly a --strict-types option (and equivalent function parameter) should be used to preserve backwards compatibility.
For example including a map doesn't require the presence of elements of that map
The practice of accepting None as a valid value for optional keys is surprising and hard to debug. I don't feel it should be accepted in a schema managed file, particularly if the strict mode is specified. Possibly a --strict-types option (and equivalent function parameter) should be used to preserve backwards compatibility.
For example including a map doesn't require the presence of elements of that map
Include schema with optional portion:
Pass because element is None, despite missing required_field
Adding the none=False field here produces the expected behaviour, it should be the default behaviour.