Docs generation fails if a file is uploaded as part of a spec about rspec_api_documentation HOT 17 CLOSED

I've just hit this issue. Is there a fix for it?

from rspec_api_documentation.

Not yet. I'm not entirely sure how we'd fix the problem. Do we snip out the upload data or leave it in bloating the docs? If we take it out then we're not really documenting the whole example response.

I thought it might be cool to detect the upload and save it out along side the docs so we can replace it with a link so people can download it.

from rspec_api_documentation.

I was thinking it could detect the upload data, and just replace it with a string saying something like "upload data"?

from rspec_api_documentation.

Also hit this, a fix would be very appreciated

from rspec_api_documentation.

I have not yet experienced this, but I will shortly.. I was here to create a different issue, but yeah, I agree with @pollingj -- replacing it with something that indicates it was a file is fine by me.

from rspec_api_documentation.

Is it possible to manually add a section to docs meanwhile?

from rspec_api_documentation.

Sure, depends on how you're hosting them though. If you're using the HTML writer just add a new link in the index page and corresponding HTML page. The JSON writer is similar, but make sure you format the example correctly so Raddocs (or similar) can view it.

I'll look into this a little bit more and see what I can come up with.

from rspec_api_documentation.

Keep in mind that the path is removed before rebuilding, so you would have to do this manually every time you generate the docs.

from rspec_api_documentation.

I did something similar by adding a controller tests outside of the acceptance specs (for a real spec for it), and did the request/response in such a way in the acceptance specs that makes it appear as though there was a file attached in the request.

eg. let(:attachment) { '[File Attachment'] }, then find and update the record with an attachment manually (only works on update). It at least simulates it in the documentation.

from rspec_api_documentation.

I think I have a working solution for this. Could everyone check out this branch and see if it works for them?

https://github.com/zipmark/rspec_api_documentation/tree/uploaded_data

from rspec_api_documentation.

Doesn't seem to support files in nested documents.

from rspec_api_documentation.

@oestrich I just put a PR in to expand upon your solution that wasn't working for a few people.

from rspec_api_documentation.

@oestrich I am having exactly the same problem with an uploaded file. I was thinking about opening a PR, but saw this thread. What is the current state of the issue?

P.S. The uploaded_data branch does not work for me. I had to update the File.open mode in order to avoid encoding problems. See here dalizard/rspec_api_documentation@94243ef

from rspec_api_documentation.

@dalizard Can you try out the branch again? Merged in @Ruxton's changes.

from rspec_api_documentation.

@oestrich It works! Any idea as to when this could be pushed to master and released?

from rspec_api_documentation.

FWIW we've been using this as part of our CI process in 3 separate projects since I sent this PR and are yet to come across any issues

from rspec_api_documentation.

Awesome, I'll merge it in later today then and push a new release.

from rspec_api_documentation.