Seems reasonable aside from a lost test?
892 | 891 | `!cmd ${roomMapping.server} TOPIC ${newChannel} :some new fancy topic`, | |
893 | 892 | `!cmd ${roomMapping.server} PART ${newChannel}`, | |
894 | `!cmd ${roomMapping.server} STUPID COMMANDS`, | ||
895 | `!cmd rubbishserver SOME COMMAND`]; |
we've lost the test for an invalid server here?
With this change "rubbishserver" is now interpreted as a command rather than as a server.
right...we still need to interpret servers here.
They are interpreted correctly when valid, but rubbishserver
matches the new regex.
Perhaps that could be replaced by rubbish^server!
or something?
Or we could have two servers configured to ensure that the first string needs to match a server.
I think it's okay to let this one slide though. We're not breaking anything anything except wrong usage of commands, and I don't think there's much of a risk of a server being called quit
or something that could land a user in (minor) trouble.
oh and
887 | 887 | ||
888 | // 5 commands should be executed | ||
889 | // rubbishserver should not be accepted | ||
888 | // 4 commands should be executed | ||
890 | 889 | const commands = [ | |
891 | 890 | `!cmd ${roomMapping.server} JOIN ${newChannel}`, |
We still need to test lower case though?
Added in 1846095
Login to write a write a comment.
Split off from #1807, credit to @funderscore1