-
Notifications
You must be signed in to change notification settings - Fork 467
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
Unreadable examples.yml #125
Comments
Another unreadable record. |
After disabling code coverage for APIPIE_RECORD rspec the yml file looks fine. We have some tests covering binary & base64 uploads, after disabling them the file is parseable again. Our CI system is now trying to load and stringify the examples file before every deploy, so an invalid file can't break the server anymore.
@Pajk what do you think of changing the overall file format to json instead of serializing a hash to yml, to parse it and serialize to json again? |
I remember a discussion about breaking the examples into smaller files, structured by controllers and actions (man I can't find it now :(, This was the first cat of the format, we have now much more input on how this could be improved. Moving to json seems like a way to go. |
I've been hitting this error for a long time at
Causing re-generation of examples to fail (until old file is removed) and of course also display fails. And this seems to happen in random manner. I quickly tested this "json-record" branch, and it seemed to fix issue. So is this fix going to get merged to master someday? |
* https://github.com/Apipie/apipie-rails: Test against ruby 2.1.1 [Fixes Apipie#125] Dump examples as json Update initializer.rb.erb
I generating the examples using:
Sometimes this produces an unloadable yaml file. If I try to load the file manually it says
The text was updated successfully, but these errors were encountered: