Benjamin Fleischer

**Comment by [jamesfzhang](https://github.com/jamesfzhang)** _Wednesday Mar 26, 2014 at 13:30 GMT_ --- :+1:

fwiw I've now removed from my `config/initializers/assets.rb` ```ruby Rails.application.config.assets.precompile += %w( apitome/*.css apitome/*.js ) ``` and added to my `app/assets/config/manifest.js` ```sprockets //= link apitome/application.css //= link apitome/application.js //= link apitome/highlight_themes/solarized-light.css...

What version are you using? RSpec shouldn't be running tests in dev. That's just how Rails works https://github.com/zipmark/rspec_api_documentation/blob/d3892cc7388460a98476734963face5a7a2ac158/lib/tasks/docs.rake

Thanks @jakehow Right now our CI process is to 1) run tests in parallel 2) build the docs and commit if they may have changed 3) push to a deploy...

fwiw, I'm researching this now myself. looks like you're on rails 6.0.2.1. I'm on Rails 5.2. did you just upgrade rails? have you ever had it working?

I think this is a duplicate of https://github.com/jejacks0n/apitome/issues/113

Issue for me appears to be that rspec_api_documentation may return the string `"[binary data]"` as the response body, and this makes apitome blow up. https://github.com/zipmark/rspec_api_documentation/blob/560c3bdc7bd5581e7c223334390221ecfc910be8/lib/rspec_api_documentation/client_base.rb#L88-L96 I'd like to propose adding...

I made a PR https://github.com/jejacks0n/apitome/pull/115 gonna test it in my app

Issue was a change in rack and naive logic in rspec api doc with poor handling in apitome

@aadityataparia new formatter `open_api_v3.0` seems right. I know this is old. was any of that work shared back?