Open Wealthyturtle opened 5 years ago
Although I believe options should allow colons (for use in strings or whatever), I do not see this as limiting what you're doing in this situation.
You could just as easily do:
every {@test} seconds:
and set the option test to 1
.
Even if (for some reason) you really, really wanted to make options for your events (although this seems wholly unnecessary to me?) you could use {@option}:
with the colon after it, to avoid using it in the option name.
I agree in principle (as it is something of a limitation), though not with the usage in your example.
- The Ability to use options inside other options this would help a lot.
That one might be harder to achieve, because it would have to check for nested options first, then handling non-nested options, then continuing handling of nested options, starting from the lowest order
- The Ability to use options inside other options this would help a lot.
That one might be harder to achieve, because it would have to check for nested options first, then handling non-nested options, then continuing handling of nested options, starting from the lowest order
I know it might be hard to achieve but it would be really useful sometimes but not really necessary all the time.
Description
Currently, options don't support colons that are at the end of the option (example: for use in periodical options)
Steps to Reproduce
Expected Behavior
For
Test
to be broadcasted every 1 secondErrors / Screenshots
Server Information
Additional Context
Perhaps get the end of an option string by testing for the end of line character?