-
Notifications
You must be signed in to change notification settings - Fork 133
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
YAML parsing error #15
Comments
I'm running into this too, but only when running in my test environment. We provide our own config/sms_fu.yml file with all the carrier values wrapped in single quotes and it works fine. However, it looks like the code here is using the sms_fu.yml provided in the templates directory when Rails.env is 'test'
So when I run my tests, this blows up. This has only become an issue since updating to ruby 2.1.0 |
Seeing this as welll |
+1 while processing templates/sms_fu.yml
|
Calling .deliver threw an error that originates in the sms_fu.yml file:
Psych is the YAML parser and doesn't play well with values starting with "@". Trying to wrap carrier values in strings (i.e. @gin.nl => "@gin.nl") didn't help. Calling YAML::ENGINE.yamler = 'syck' fixed the issue for me:
http://stackoverflow.com/questions/4980877/rails-error-couldnt-parse-yaml
What's the best approach here? Could we set YAML::ENGINE.yamler = 'syck' in the context of this gem without affecting the YAML settings of every app that installs it?
The text was updated successfully, but these errors were encountered: