If the config.yaml contains unexpected types such as an int where it expects a list, you get a big ugly stack trace.
It is possible in some cases to cast to the expected type however sometimes that can leave the user with unexpected results unless every possible case is handled.
At the very least I would like a nice friendly error here but the code for this is spread across a few files, and can even happen in user extensions, so I'm not quite sure how best to handle this at the moment.
If the config.yaml contains unexpected types such as an int where it expects a list, you get a big ugly stack trace.
It is possible in some cases to cast to the expected type however sometimes that can leave the user with unexpected results unless every possible case is handled.
At the very least I would like a nice friendly error here but the code for this is spread across a few files, and can even happen in user extensions, so I'm not quite sure how best to handle this at the moment.