-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Space toleration outside optional bracket #100
Comments
@kirsle What do you think about space tolerance for optionals? |
This form should probably still work:
In that example it'd probably be a typo, but I could see users deliberately not including a space because they want to match multiple prefixes or suffixes on a word and don't want to have to repeat the entire word multiple times, like However, consolidating 2+ spaces in the trigger down to 1 space would sound reasonable. I couldn't imagine someone relying on the user needing to type 2+ spaces between words to match a trigger. The regexp could be like |
The optional brackets accept multiple spaces between optional and main text (like between
hello
and(you|me)
in 1st trigger). But if it happens that space is missing (likely an unnoticed typo), the matching for 2nd trigger will behow areyou
andhow areu
, but NOThow are you
.The text was updated successfully, but these errors were encountered: