Jason Walton

And, cookies default to "form", but they aren't *really* "form". An array encoded in "form" with `explode: true` is encoded as: 'color=blue&color=black&color=brown' (this is the example [from the spec](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md#style-examples)) but...

Using cookies as parameters is weird, and I know there's a history of debate about whether to include them in the spec or not in the first place. I'm not...

Well... it depends on what you count as the "rendered" version. If you have a header pameter, for example: ``` X-MyHeader: 5 ``` The "name" of the parameter is right...

If we're using the encoding as described on swagger.io, then yes, and explode is true, the parameter name disappears and it becomes: ``` Cookie: x=7&y=hello ``` I mean, first when...

Or, to put this more succinctly: RFC 6265 says a cookie is: ``` cookie-header = "Cookie:" OWS cookie-string OWS cookie-string = cookie-pair *( ";" SP cookie-pair ) cookie-pair = cookie-name...

Yeah, by "a form encoded string", I really meant "a RFC 6570 form-style query expansion". :) Although, now that I go back an read RFC 6570, in order to be...

Oh, hang on, I think this might be my fault... :P

The problem happens when you try to use a custom storage directory for Graphite: ``` docker run -d --name statsd --restart=always \ -p 8080:80 \ -v /mnt/graphite-storage:/opt/graphite-storage \ -e GRAPHITE_STORAGE_DIR=/opt/graphite-storage...

Can fix this by running: ``` docker run --rm \ -v /mnt/graphite-storage:/opt/graphite-storage \ -e GRAPHITE_STORAGE_DIR=/opt/graphite-storage \ hopsoft/graphite-statsd \ python /opt/graphite/webapp/graphite/manage.py syncdb --noinput ``` before I run graphite "for reals". You...

> I would need a minimal reproduction step. @mshima This is not *quite* minimal, but this branch of my generator has the problem: https://github.com/jwalton/node-jwalton-generator-typescript/tree/upgrade-yeoman In my case, if you try...