GraphQL Field Alias Spec Compliance


Currently Realm GraphQL only allows field aliases on top level queries, and not on keys. An error will get returned stating:

"message": "runtime error: slice bounds out of range [-1:]"

Are there any plans on compliance with this GraphQL specification? It would be very much appreciated.


Can I get an official response on this? A lot of the tooling that we use at the agency I work with have fully compliant GraphQL specs which are causing errors when queries are being sent to the Realm GraphQL service. Thanks.

Hey @Andrew_Edgar - I’m sorry for such a late response. This isn’t an available feature at the moment - can you provide more insight into why you want to use @alias and the general need for full GraphQL compliance? While this isn’t on our roadmap right now, Adding it here would help us gauge interest - Realm: Realm GraphQL (19 ideas) – MongoDB Feedback Engine