[Resolves #91] Invalid characters on suffix

[rpbaltazar]

Describe the change

On the conversion of the user input, instead of blindly generating the regex for matching based on the configured positive value we ensure that the value for positive is escaped if needed, by invoking Regexp.escape.

Why are we doing this?

Building the regex blindly based on the user suffix param, in case he/she uses characters that conflict with the regex definition itself, it makes the prompt crash.

Benefits

When adding this, the suffix option for the prompt will support characters that otherwise would crash the regex definition.

Drawbacks

None that I can think of

Requirements

Put an X between brackets on each line if you have done the item:
[x] Tests written & passing locally?
[x] Code style checked?
Tried to follow the patterns I've identified in the existing codebase but i might have missed something.
[x] Rebased with master branch?
[] Documentaion updated?
There is no need for updated documentation in my opinion

[coveralls]

Coverage increased (+0.008%) to 97.042% when pulling 2f1464f on rpbaltazar:invalid-characters-on-suffix-91 into 0c1ab30 on piotrmurach:master.

[piotrmurach]

Thank you! ❤️