Matt

I'm not entirely convinced about this. If my request contains a JSON, then my whole request body should be of type JSON and Rails would parse that for me automatically...

This sounds interesting and it would work similarly to "Form" objects. I'd like to understand what `rails_param` can do to help with this though. You can already move validation rules...

That looks cool and similar to other gems behaviour, though we'd need to be extra careful with performance as Ruby can be quite slow with reflections. Test and documentation coverage...

Thank for taking a stab at this @a-chris. I had a quick look to provide some early feedback, I'd love to hear from @ifellinaholeonce as well. > Let me know...

@gabrielres I like the idea but we're planning a refactoring of validations based on ActiveModel so I'll come back to this after we're done with that.

I like the idea of having a custom message option, but the refactoring looks too much convoluted to me (and very much Java-like...). Moreover, we're planning a refactoring of validations...

Thank you for considering `faraday` for this! Following @catlee's input, we've just released v2.5.1 which supports a new API to access response codes while streaming responses 👍 I hope that...

That makes sense to me. Similarly to the [argument filter](https://github.com/iMacTia/sidekiq-logstash/blob/master/lib/sidekiq/logging/argument_filter.rb) we could have a `job filter` that by default logs all jobs, but can be instructed to only log some...

+1, still an issue on the latest version 😕

Gentle nudge on this one, I'm not pretending to see a PR to get this fixed, I merely want to kick off the discussion to understand if this makes sense...