Erik Wrede

@ddelange @SuperSandro2000 thank you for linking the other issue!

Thanks for the effort! Shouldn't defining the union work without having to specify `possible_types` for each ObjectType in the union, just like the current example suggests?

What version of Graphene are you on? This works for me (3.0): ```python from fastapi import FastAPI import graphene from starlette_graphene3 import GraphQLApp, make_playground_handler class A(graphene.ObjectType): a = graphene.String() class...

And it should be working just like that due to this method: https://github.com/graphql-python/graphene/blob/72c2fd5ec38af595519b2ab334696397760d2d81/graphene/types/union.py#L74 EDIT: I see what you're doing, you're initializing one_object instead of the objecttype while I'm creating a...

Well, docs need a general overhaul so issues like you described with the object types have clear solution. I like your documentation on unions, but I think it should include...

I think you'll need to create a resolver returning root.actor.login/resolving the actor first depending on your setup.

Sorry for the late reply, didn't get the notification. Looks interesting! Do you want to open a PR and integrate it into the main repo?

Why do you consider this to be a bug? Can you provide a scenario where this appears unexpectedly/because of a bug?

New issue for type hinting is #1454. Will start addressing this soon.

@ulgens Do you have time for a review?