campaigns: Turn queries into noops when ID == 0, return err in mutations (!10976) · Merge requests · Administrator / sourcegraph

Created by: mrnugget

I just ran into this when trying to debug why a test in another branch didn't work.

In other resolvers (in graphqlbackend) we often return nil, nil when something cannot be found, so I followed that here.

But I'm curious as to what the expected behavior of a GraphQL API is in this case — should we return an error?

campaigns: Turn queries into noops when ID == 0, return err in mutations