Allow integer and boolean types in JSON Configuration Variables Feature
JSON Configuration Variables Feature only support string substitution at this time. At least integer and boolean type should be supported as well.
Ryan Holmes commented
I agree with this, right now they are treated as string and this can break things if developers assume the configuration file will retain the same datatypes. Right now, if we wanted to evaluate a bool config, we have to parse it as a bool first
Agree, possibly allow the ability to validate variables using regular expressions?