Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Matching and Linebreaks #35

Open
meowgorithm opened this issue Sep 13, 2017 · 2 comments
Open

Matching and Linebreaks #35

meowgorithm opened this issue Sep 13, 2017 · 2 comments
Labels
bug

Comments

@meowgorithm
Copy link
Contributor

I've been noticing that user input with linebreaks seems to not match anything at all, not even the topmost catch-all rule. I've been solving for this in the meantime by stripping line breaks before passing the input to RiveScript, but wondering if this is a bug or intended behavior?
@kirsle
Copy link
Member

kirsle commented Sep 13, 2017

It's a bug. At the very least the + * trigger is supposed to match it, as that even matches completely empty messages.

@kirsle kirsle added the bug label Sep 13, 2017
@meowgorithm
Copy link
Contributor Author

Awesome and good to know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@meowgorithm @kirsle