State model variables that are named the same as config slots get initialized by the config slot value (unexpectedly) #5438
Description
If you have a stateModel variable named the same as a config slot variables, the state model will actually be initialized to whatever the config slot value is.
This is actually surprising to me. This could be perceived as 'helpful' behavior ...it is a good thing to get initialized by config automatically...maybe...but i think it is somewhat unexpected. It might be part of the types.union "dispatcher" system to decide what state model to use for a particular config
At this stage, it might not even be worth it to change this behavior but just wanted to document it