Tobias Lohse

Maybe the easiest way would be to pass a layout component to both `After` and to `render` (just like `document`). I think that should work for both: non switch routes...

@jaredpalmer I whipped up a quick PR #173 of how this could work

There’s a PR in flight for this, so it’s not stale.

PR pending

yes, switching to next, haven't regretted it for a second

I tried to build something into the direction myself, but I can't get it to work. Maybe I'm missing some understanding for how the functions are called. https://github.com/MrLoh/graphql-lodash/blob/ddeff5e4dccd91f4e4c0b15c95a71c12824d7d19/src/transformations.ts#L43

maybe it should better look like this: ``` movie { title releaseDate @_(asDate: none) } ```

I'm sending Dates over graphql and since Date objects are not directly supported, I need to parse them in the query, which in the prop transformations in Apollo, which is...

In another part of the API, I'm getting geo coordinates back as Strings, but need them as Numbers, which leads to similar code.

But I think dates are the most common use case, since you can't send them natively and apollo doesn't provide an easy way to decode them https://github.com/apollographql/apollo-client/issues/585