This is just the base of the validator. Right now all it does (after checking that the file exists and is a yaml, of course) is check for the expected keys and types (basic types, no enums yet and not focusing on min/max or list types or if it's required).
The next PR will include an updated api.py (possibly split into a folder for scenes and states, tbd) that includes additional parameters for each key (see the comment at the top of api.py). This should make adding and changing enums and other parts of properties simple and fast in the future.
This is just the base of the validator. Right now all it does (after checking that the file exists and is a yaml, of course) is check for the expected keys and types (basic types, no enums yet and not focusing on min/max or list types or if it's required).
The next PR will include an updated api.py (possibly split into a folder for scenes and states, tbd) that includes additional parameters for each key (see the comment at the top of api.py). This should make adding and changing enums and other parts of properties simple and fast in the future.