Re: [Rails] Programmatic way to find the bad spot in a YAML file?
"Phlip" <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <01a801c7deed$36754920$6801a8c0@Marley> |
[Please fix the mailing list settings to reply to the list by default] TRANS wrote: > Looks like it's interpreting a field that looks like a date but isn't? > With Syck I believe any plain scalar of the form 9999-99-99 is going > to be made a date --or at least try to be. In your case it fails. > > To fix, make sure any entries like this are in quotes. That's the fix for the inner problem. The outer problem is fault tolerance. Our programs can only be as user-friendly and fault-tolerant as their libraries. The lower the library, the more tolerance. I can't ask my customers to enter all their data in YAML until I can highlight the line and column of their errors for them. -- Phlip http://www.oreilly.com/catalog/9780596510657/ "Test Driven Ajax (on Rails)" assert_xpath, assert_javascript, & assert_ajax ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/