Dmitry Polushkin

Seems like it works perfectly. @bolahanna44

What is the problem here actually?

As I know it at least doesn't work in Firefox. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Trailer tells it's supported in all the major browsers.

Had the same issue, solved by `stringify_keys`; but I think this one should be solved inside addressable it self.

@sporkmonger I agree, but in that case the small note should be added to the documentation, as keys should be strings, and not symbols because of the ambiguous while sorting...

I'm also interested in this topic. Looks like only one way of doing that is to share translation data on the REST end-point and download it on the server/client side...

I have found the following approach works good in our project: reuse `permit` method of the strong params directly inside the `params_filter` scope. Policy `params_filter` on steroids with help of...

https://github.com/glebtv/httpclient/commit/7f5208af0397fe42b15c9e10ea3736c451a4f62d - this one? Tests must be written more carefully.

Yes, you are right, my mistake - limit is for the response. - Can I make a PR for this gem or should I make an extension outside of this...

Problem is still exists. The reason of it that worker is triggering save on model, and it updates `updated_at` field. `:updated_at` and `:hash` interpolators are related from the model updated_at...