Curt Micol
Curt Micol
Hmm, so this might be breaking... going to check with some people I know using this.
That's a valid question. Two things I can think of: - Service handlers ack'ing pages and resolving upon success (I need to think of this a bit more) - Frontends...
Love the UID on request. I use that idea on every service I build at work, makes life so much easier. :) Also, you could build in verbosity around SOGGY_ENV...
I recommend a version 4 UUID like Ruby's `SecureRandom.uuid` generates.
[This](http://www.ashishbanerjee.com/home/go/go-generate-uuid) might be helpful.
@dbrain I just discovered your project recently. Looks great. I'd recommend GOLANG_ENV, or even the more specific SOGGY_ENV to avoid name collisions. But I recommend keeping it simple at first,...
Commented in the gist.
Trying to figure out why you are seeing that behavior? ``` ruby projects/scrolls master! : irb -Ilib irb(main):001:0> require 'scrolls' => true irb(main):002:0> Scrolls.log({"query_string" => "param=value"}) query_string="param=value" ``` It shouldn't...
Ah I see now. Hmm, let me take a look.
Alright, I see the issue and have a fix for your first failure case. The next three are interesting, I'll have to work on those a bit.