Feature: Default GraphQL Enums from Python Enums.

[nrbnlulu]

Feature Request Type

• Core functionality
• Alteration (enhancement/optimization) of existing feature(s)
• New behavior

Description

Currently to register a GraphQL Enum from an existing enums that resides elsewhere in your code base
you need to do the following ~

from somewhere import MyEnum

MyEnumGQL = strawberry.enum(MyEnum)

@strawberry.type
class Foo:
	bar: MyEnumGQL

This results in a pyright error that can be fixed like this

from somewhere import MyEnum
if TYPE_CHECKING:
	MyEnumGQL = MyEnum
else:
	MyEnumGQL = strawberry.enum(MyEnum)
	
@strawberry.type
class Foo:
	bar: MyEnumGQL

It would be nice if we could just use a default GraphQL implementation of the enum on the fly
so that the strawberry.enum call would not be needed.

from somewhere import MyEnum

@strawberry.type
class Foo:
	bar: MyEnum

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[erikwrede]

I like this! We would need some sort of a registry to ensure we don't duplicate enums across types, but other than that it's a very straight-forward devX improvement.

The only "issue" I see is documentation - we need to make a decision on wether we want to include docstrings of the original python enum in the GraphQL schema, and we need to be aware that specific enum values are not annotatable with their own docstrings in python.

[patrick91]

I like this! We would need some sort of a registry to ensure we don't duplicate enums across types, but other than that it's a very straight-forward devX improvement.

Good point! We might also think of this in the context of Strawberry Django (and other integrations)

Would we make a registry per schema, right? 😊

[erikwrede]

Yes, per schema. We could directly use this for Django and Sqlalchemy to reduce redundancies there :)