Christian Legnitto

@tomhoule you should have an invitation to join the org

Potentially interesting: https://github.com/davidpdrsn/juniper-from-schema

I just did a juniper PR that supports going from a juniper schema to the graphql schema language as well as a `graphql_parser` `Document`: https://github.com/graphql-rust/juniper/pull/324 Hopefully it should help these...

FWIW latest master of `juniper` now has built in support for the introspection query. One can easily generate a `schema.json` for use with `graphql-client`: https://github.com/graphql-rust/juniper/blob/master/docs/book/content/advanced/introspection.md

I was thinking users make a workspace with two crates: * my-backend (containing `juniper` and the schema definition) * my-frontend (containing `graphql-client`) And then have `my-frontend` have a dev dependency...

With a build system like buck/bazel you could have a CLI tool depend on `my-backend`, generate a binary, run the binary via a genrule and output the `schema.json`, and then...

Ya'll may be interested in https://github.com/srijs/rust-aws-lambda/tree/master/aws_lambda_events. I generate the event structs from Go. I'm going to publish it as its own crate soon.

I did: https://github.com/srijs/rust-aws-lambda/tree/master/aws_lambda_events. It doesn't have any deps on a particular rust framework and is auto-generated from the official go typedefs. It even autogenerates tests and uses the example json...

@softprops Zero deps on the parent project. The parent project consumes it and reexports. I was doing my own runtime with gob encoding and decided to join forces. It also...

@softprops FWIW I published an initial version of the events package: https://crates.io/crates/aws_lambda_events