Maarten van Vliet

Absinthe 1.7.1 is released with the fix for this. When I run the `break-composition` branch link above I get the following message: ``` == Compilation error in file lib/products_web/schema.ex ==...

Both [Absinthe](https://github.com/absinthe-graphql/absinthe/pull/1227) and [Dataloader](https://github.com/absinthe-graphql/dataloader/pull/152) use the `OpentelemetryProcessPropagator.Task` in their main branches (unreleased), so the set_current_span/1 can be removed afaict.

I suspect this happens in the `ObjectMustImplementInterfaces` phase. It does covariant checking there and can get quite difficult to follow. There's also some normalization happening. I don't have time to...

Glad you find it useful. I no longer have the need for this feature, so feel free to work on it. One thing I was thinking a while back is...

Gonna close this in favour of https://github.com/absinthe-graphql/absinthe/pull/1295

I wrote a post a while back on how to accomplish this https://maartenvanvliet.nl/2022/04/28/absinthe_input_union/ with Absinthe. It can be accomplished right now without any changes to Absinthe itself.

I had a quick look. There's some logic happening to make the function specs more succinct by unnesting them. In cases of name collisions this can give bugs. I tried...

The https://github.com/beam-community/stripity-stripe/pull/786/files#diff-96e6fda24e580cda6be0289146011cf77e2bf6d46f3afb82dc7c628d03827ff4R2 branch has a way to override the function names for these collisions. If you find a better way I'm all for it.

The way the Go SDK does it, will require quite some work in the generated code. Comes down to the same thing in other SDK's by making it a special...

I agree that it's aesthetically less pleasing to have this one exception to how it's done the sdk and naming this function `retrieve_by_id`. Other options I've considered were to name...