0👍
✅
Well I finally changed my mind and decided to perform the mutation on the STAGE instead of doing this on the TICKET
so that I can send the source stage and the target stage with their updated list of tickets as result of the mutation. By writing all the question I realized it would be easier that way…
Indeed the result of the mutation is then : [source_stage, target_stage] so the output type is now graphene.List(my_type).
By doing this I don’t have to change manually the stage ticketIds manually after the mutation in an update
statement since it updates by itself correctly.
Source:stackexchange.com