[GraphQL] Make id field optional for custom mutations#2738
[GraphQL] Make id field optional for custom mutations#2738lukasluecke wants to merge 1 commit intoapi-platform:mainfrom
Conversation
0ea74ff to
de803af
Compare
|
@alanpoulain What do you think? (test failure seems to be unrelated) Probably should be in 2.4 and not master, but I'll leave that up to you 🙈 |
|
I think we should have a Behat test for this feature. |
|
I will try to add the test later today 🙂 |
de803af to
e824e6b
Compare
|
@alanpoulain I added a simple test for this change 🙂 |
a3130cf to
e313aea
Compare
|
@alanpoulain @dunglas I rebased this onto the newest changes again, could we maybe get this merged? Some tests seem to be failing for some unrelated reason, the others I will look into shortly. |
|
I'm not sure about this one. Now you can define your own arguments for your custom mutation. |
e313aea to
b79a347
Compare
|
I don't think that the current possibilities for custom arguments are really "usable" for this, as I'd have to re-define all arguments just to get rid of the required ID. However if you think that the way forward would be better custom arguments, I'll try to work on that instead (might take a little longer though) 🙂 |
|
Hello, is it possible to merge this change? I really need overwrite create mutation in my project. |
|
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. |
|
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. |
All other mutations (except
create) get an optional id field to allow different kinds of custom mutations.