Reserved prefixes for custom or lambda mutations not in documentation

I found nothing in the documentation warning that lambda mutations cannot begin with “add” or “update” even if the full name is unique.

I have a working, simple lambda mutation, somethingNew. When I change the name of the mutation (both in addGraphQLResolvers() and in the schema, obviously) to begin with “add” or “update”, I get the errors:

  • Cannot query field "addSomethingNew" on type "Mutation"
  • Cannot query field "updateAVeryUniqueNameThatShouldNotBeReserved" on type "Mutation".
1 Like

@docs I think this is something that must be added.


Agreed, we’ll update the documentation on this. Thank you for flagging this gap @jlangree.

1 Like