Closed jywarren closed 7 years ago
Alternatively, the ability to pass an onResponse()
or after()
method in the images
options object, to enable custom response parsing?
This changed quite a bit actually
See bureaucracy
Oh, cool -- do you mean potentially to use bureaucracy in woofmark
code or just in my application code? Thanks!
Woofmark already uses bureaucracy now. That's what I meant
Awesome, thanks!
On Jul 21, 2016 4:24 PM, "Nicolás Bevacqua" notifications@github.com wrote:
Woofmark already uses bureaucracy now. That's what I meant
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bevacqua/woofmark/issues/30#issuecomment-234372442, or mute the thread https://github.com/notifications/unsubscribe-auth/AABfJ0fQTDeo3QzO5mTU1x84iXUwWyU9ks5qX9VKgaJpZM4Itx7l .
Closing this now for an issue in bureaucracy
: https://github.com/bevacqua/bureaucracy/issues/1
Thanks!
I'm responding (from Rails) to an image upload, and when I send a response back it's parsed as a string, not JSON, oddly. The headers seem right:
And the response body is:
However, I had to add the following to line 180 of Woofmark's
prompts/prompt.js
to getbody.href
to return anything:Do you think I'm doing something wrong in encoding my server response, and/or would adding an extra check and ability to parse into JSON be a useful extension to Woofmark's abilities?
Thanks!