Skip to content

Update to Doctrine ORM 3.2 #10257 #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 27, 2025
Merged

Update to Doctrine ORM 3.2 #10257 #73

merged 3 commits into from
Apr 27, 2025

Conversation

PowerKiKi
Copy link
Member

@PowerKiKi PowerKiKi commented Jul 11, 2024

Blocked by Ecodev/felix#23

If the custom types container is correctly configured to be able to
create a `\GraphQL\Type\Definition\EnumType` matching the FQCN of a
PHP native enum, then `graphql-doctrine` will be able to use PHP native
enum in output, input and filters.
Instead, return an empty string, which will have the same effect as
returning null. Removing null removes the confusion semantics difference
between null and empty string. There never was any difference, and
null should never have been allowed.
@PowerKiKi PowerKiKi merged commit 9ce071d into master Apr 27, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant