escape regexp chars in configuration strings?
Trott opened this issue · comments
This would be a breaking change, but the API may be approaching being powerful enough that we can remove the surprising treat-strings-like-regexps behavior.
Or maybe require people to supply a regexp if that's what they want, and otherwise it will be a string? Handling a regexp will probably have to be a whole lot simpler. People will probably have to deal with word breaks themselves for example? Maybe not, but possibly.
Or make it a configurable option? Now that we've added ignoreNextTo
, I'm suddenly all about adding options rather than trying to make it "just work"....
Going to close this. Can revisit if this is ever an issue for anyone.