Hi @MichelDiz
Thanks for the answer. I have replied to your answer in my Bug Report. Unfortunately it did not work.
To keep this topic in sync and readable for potential other people with the same problem, I copy and paste my answer here as well:
In my opinion, this contradicts with the user intention. I guess the intention of this mapping is that we can use the same aliastwice in two different blocks but I do not think that this is the user intention. A user can alway pre/postfix an alias to make sense for his use case (eg. by adding the corresponding typename, the query name, etc.). This way value variables could simply be stored as a key/value pair and used everywhere in an upsert mutation.
Therefore, since this is not a bug, we can safely resolve this issue. Maybe you could update the documentation slightly so people don’t get confused here.
Would it be possible that you show me where the actual mapping takes place in the Dgraph source? If I have time I could check if it would be worth a feature request / pull request.
I have change the post type from Issues/Bug Report to Users/Dgraph Cloud.
Cheers!