David Pedersen

> Boxed Services is non trivial > > This can be solved and I might add it as an experiment to tower-async. But the only way I see how for...

> In my opinion, this is probably the best approach, since we get to maintain our current flexibility while still allowing use with unboxed async/await when the user is willing...

Not sure there is a good way to support both attributes that you want on the trait and the impl, and attributes you only want on the impl. To me...

Hm feels like a lot of new stuff just to support something like this 😕 Maybe writing your own extension trait is better for this use case.

If you're up for making a PR thats cool with me! Although I think the syntax should be ```rust #[ext] impl i32 { // apply `#[tracing::instrument]` to the method in...

Update: This is in the works [here](https://github.com/davidpdrsn/juniper-eager-loading/pull/63) but I'm running into some tricky lifetime issues. I don't currently have much time to dig into it.

After some further research it turns out I didn't actually need this feature after all. When someone explicitly asks for it we should consider it then.

Alright. I’ve reopened the issue. Dunno when I’ll get time to look into it. You’re welcome to give it a shot 😊

Are you using a git dependency for juniper-from-schema? The version that is on crates.io doesn't support juniper 0.15. There has been a bunch of breaking changes as well. [The changelog...

Using a [git dependency](https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-git-repositories): ``` juniper-from-schema = { git = "https://github.com/davidpdrsn/juniper-from-schema.git", branch = "master" } ```