We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had the misfortune the last few days to believe that the vocabulary csv files were not operating correctly.
Apparently whitespace is not stripped around fields. So "test, test2" leads a row which is parsed, but not turned into a functioning command.
The text was updated successfully, but these errors were encountered:
this might be the same as talonvoice/talon#199, which was just fixed
Sorry, something went wrong.
I replicated this behaviour using that Talon release, it's still an issue.
I have a fix for this, I just need to make a PR for it, I should get to it sometime tomorrow.
Successfully merging a pull request may close this issue.
I had the misfortune the last few days to believe that the vocabulary csv files were not operating correctly.
Apparently whitespace is not stripped around fields. So "test, test2" leads a row which is parsed, but not turned into a functioning command.
The text was updated successfully, but these errors were encountered: