Howard M. Lewis Ship

Let's not merge this until the other documentation PR (https://github.com/pedestal/pedestal-docs/pull/160) is merged and deployed.

Thanks for the update; been busy here. I'll try to digest what you have posted above.

I'm struggling to find time to come back and finish reviewing this. I want to test what happens when the injected Fed 1.0 directives and types are _not_ filtered out...

The process of getting code form the tutorial example app into the lacinia documentation is ... tortuous.

I'm very interested in this; it's just a bit big for a bug fix release, so it'll wait for 1.3 rather than 1.2.x. I don't mind mixing a little bit...

@tomekw Given Paul's direction and analysis, this does appear to be an issue in Pedestal to be addressed. You had previously offered to work on a patch, we'd love to...

I don't understand the root of this problem: under what circumstances is a java.util.Map being passed around the Pedestal code, and where? What does AWS have to do with it?

Ok, so I'm unfamiliar with the AWS stack (didn't use any AWS at Walmart, would you believe :-)). So there's entrypoints into the Pedestal code where the inputs are java.util.Map...

``` (reduce-kv conj [] (doto (HashMap.) (.put "a" "a") (.put "b" "b"))) => ["a" "a" "b" "b"] *clojure-version* => {:major 1, :minor 11, :incremental 1, :qualifier nil} ``` Looks like...

That's at least part of the problem solved, but I'm not sure about the rest.