Ranges in TOML files do not work when datatype not equal to numeric/integer.
bald123 opened this issue · 0 comments
When a range of type integer is declared in a strategy TOML file, all possible combinations seems to be calculated correctly. For example, a TOML file having the following setting:
StopLossPercentage = 2..5:1 OR StopLossPercentage = 2,3,4,5
creates 4 backtests, which is correct. When the datatype is of type boolean or string, this does not seem to work. For example:
StopLossStrategy = "regular","trailing","none" ==> creates error during script, "invalid character: , "..
StopLossStrategy = ["regular","trailing","none"] ==> only seems to be considering the first one.
Same goes for boolean:
StopLossLimit = [true, false] ==> not working, only seems to be considering the first one.
Etc. It looks like only numeric/integer ranges/arrays are interpreted correctly?