I had them in there because the `haslog` parameter has both boolean and string options (`True`, `False`, `100%` and `<100%`). I wanted people to be able to configure the plugin with YAML-style truthiness (like `1`, `true`, `True`, `yes`, etc.) instead of being limited to a certain choice, but still allowing to chose other options.

This makes it so it will accept `haslog: yes/true/1`, as well as `haslog: 100%` in the config file.

Doing it that way had the side effect of needing the other True/False choice to also be dictionaries.