-
-
Notifications
You must be signed in to change notification settings - Fork 869
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
Calling GraphQL DeleteMutation ignores serialization groups and causes error #6432
Comments
Update: it seems it has nothing to do with custom Provider/Persister, but with serialization after DeleteMutation(). Obvious normalizationContext and denormalizationContext defining groups has no effect.
fails with ""Cannot return null for non-nullable field "Greeting.name"". serialize: false (a commented line) helps to avoid error but also gives no output. Issue title updated. |
don't you need to do something like #6354 ? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
API Plaform: v3.3
Description:
Calling
produces
while name is defined as non-nullable.
Expected behavior:
An output like this:
Entity/Greeting.php
Notice: ApiResource has totaly valid DataPersister and DataProvider defined.
State/DataProvider.php
State/DataPersister.php
Here's the repository reproducing mentioned bug: https://github.com/danaki/api-platform-grapql-delete-mutation-bug-demo
The text was updated successfully, but these errors were encountered: