Simone Carletti

I've just landed here, trying to understand the reason of the hanami warnings. I also read http://stackoverflow.com/a/34275638/123527, and specifically > As I said above, current URI.encode is wrong on spec...

@cllns @AlfonsoUceda FYI there is also another solution, that doesn't require to bring in the Addressable dependency. Simply replace: ```ruby class HttpRouter class Request attr_accessor :path, :params, :rack_request, :extra_env, :continue,...

I'm not very familiar with how hanami/controller deals with the router. I would not recommend to override an entire initializer for the long term solution, but given this library seems...

> How the auth/whoami/success.http which you're using is structured? It's essentially a standard dump of an HTTP response. You can get one using ``` $ curl -i www.google.com > response.http...

All HTTP verbs essentially work in the same way. You can see some fixtures here. https://github.com/aetrion/dnsimple-ruby/tree/master/spec/fixtures.http In some cases, like a DELETE that results in a 204, the body may...

@parroty great. At this point, I think I'll provide a PR we can use as a starting point for a discussion. I just wanted to quickly check if you were...

I made exactly the same commits a few weeks ago in my custom fork at http://github.com/weppos/trample/

I am open to consider automated tagging, but it will need to behave exactly how a new release behaves today. Including: 1. [Updating the CHANGELOG](https://github.com/weppos/publicsuffix-go/blob/main/CHANGELOG.md) 2. [Updating the version](https://github.com/weppos/publicsuffix-go/blob/4dfd8dc5e0e4cbddee39f37116410807a23292f6/publicsuffix/publicsuffix.go#L23) 3....

> what would be the event triggering this process? That's a great question. I was reflecting on this question, and I realized that automating the release upon a PSL update...

Hi @rjbordon , thanks for your proposal. I have thought a bit, and at the moment I am afraid it may just not work with the current workflow. As you...