This post is quite old, but it lead to interesting insight in respect to Dgraph and GraphQL. The development team flips between “we can’t do this because it would brake the spec” and “we know it isn’t spec, but it’s just how we do it anyways”… And it has been inconsistent over the years. In areas where it could break the spec and get away with it like here, it was decided at the time that it was not worth it. But forcing unique values in lists without order preservation (aka sets)… Oh well, it’s how Dgraph handles sets. It’s fun figuring out all of these odd edge/normal use cases as you start using Dgraph.