David Pedersen

This isn't currently possible because graphql-parser doesn't provide spans, but only positions. I have asked how they feel about adding spans https://github.com/graphql-rust/graphql-parser/issues/40.

Yeah that sounds like a useful feature. I have indeed seen +1000 line schema files. I'm actually thinking about removing the procedural macros and moving entirely to doing things in...

Pulling in glob is fine. I also prefer glob patterns like `schema/*.graphql` over just a directory 👍

@acelot Nope. I haven't had much time to work on juniper-from-schema for some time. https://github.com/davidpdrsn/juniper-from-schema/pull/138 does appear to fix the issue but I haven't reviewed it. If you really want...

Juniper-from-schema always uses chrono when generating code for dates. So if you want to use some other date type you need to accept the chrono value in your 'field_*' methods...

This one shows a field that returns `Date` and `DateTimeUtc` https://github.com/davidpdrsn/juniper-from-schema/blob/master/juniper-from-schema/tests/compile_pass/dates_and_times.rs

Did that example help?

> As a final note, I strongly believe that proc/derive macros shouldn't be used unless you have a really good reason. And even then, it's probably a bad idea. While...

@0xdeepmehta No. I still have to review the PR.

I'd say this has been solved by https://github.com/tokio-rs/axum/pull/1751. TLDR: in axum 0.7 the `B` type parameter has been removed and we instead use our own `Body` type. So adding new...