Kai Ren

@timoreimann @viveksinghggits actually, I have some ready Helm chart, which we use internally. So for @viveksinghggits not having a fresh start, I'll issue a PR shortly, where will give him...

@petar-dambovaliev I'm going to cut such corner cases off with new machinery design in #1072, which won't contain such panics.

@haarts definitely not the first thing on my agenda, but I'll try to include this into new `0.16` major release.

@JonRCahill @GavinMendelGleason this topic has been araised multiple times already across issues (https://github.com/graphql-rust/juniper/issues/143, https://github.com/graphql-rust/juniper/issues/105, https://github.com/graphql-rust/juniper/issues/364). Unfortunately, seems to be no handy way to have any lifetime parameters in `Context` type...

@chirino yes ```rust #[derive(GraphQLInputObject)] struct InputObj { val: serde_json::Value, } struct Human; #[graphql_object] impl Human { fn output() -> serde_json::Value { } fn input(arg: serde_json::Value) -> bool { } fn...

@chirino > I did included a test that shows how you can create a wrapper type around serde_json::Value that provides that type info. Does it worth to have such a...

@chirino go with the names you think are best. I'll bikeshed them in the final review if a better naming will come up in my mind. > Also not sure...

@chirino thanks! I'll look at it in few days.

Just to keep everybody up-to-date: This PR is not abbandoned. I'm working on it right now to extend the work dony by @chirino. It will take quite a while, because...

@chirino unfortunately no, but thank you. You've already done so much 🙇‍♂️ I just need to somewhat extend that, fix some edge cases and polish. It will be harder to...