Closed vassilevsky closed 3 years ago
Hey vassilevsky, Thank you for your contribution :) Your described use case is exactly why we started the project :)
As you described you already have a workaround for the problem (in fact that's originally why we put that option in :D)
The response handling is like top priority in refactoring order of the code, so I will dig into this within the next days 🖖
Hello 👻
First of all, thank you for this useful gem. It brought piece between front-end and back-end developers in our team 🙏
We use Apipie to document our API. We mount it at
/apipie
in all environments except production. It loads a bunch of static files to style API docs nicely. Examples:Naturally, we've enabled serving them from Rails because those are the only assets our app has — it's just an API server. Enabling the Asset Pipeline for them seems like an overkill.
Sparrow breaks serving these assets.
When Sparrow is enabled, this is what happens when you request a static file:
In other words, it dumps a Ruby representation of the response object rather than its actual contents.
We've solved this problem for us by excluding
/apipie
in the configuration:I hope this information helps you fix response handling 🖖