@nilan I’m getting

Error: Cannot return null for non-nullable field CartItem.id.

for a simple mutation - I’ve found a few older threads about this but I wanted to see if you had ideas on what this might be

Hey @wesbos, for some reason your resolver returns

null

but is supposed to return something non-null. Can you share your resolver implementation so we can figure out why this is?

async removeFromCart(parent, args, ctx, info) {
    return ctx.db.mutation.deleteManyCartItems(
      {
        where: {
          id: args.id,
          user: {
            id: ctx.request.userId,
          },
        },
      },
      info
    );
  },

The only reason I’m using

deleteManyCartItems

here is because I want to query based on the item ID and the Users ID - so maybe that is it?

deleteManyCartItems

only returns the field

count

ohhhh

it doesn't return a field of type

CartItem

Is there another way to delete something by provding two inputs?

the item id is already enough, is it not?

well I don’t want anyone to be able to delete anything, so I rather not query the item, check the user, and then delete it

I see - you can use that logic, if you adjust your schema accordingly so it returns

count

okay that makes sense - I’ll do two queries then

Looks like half of the projects are about ecommerce stuff 😅

😄

half the world is ecommerce 😄

Would save a lot of time if we did a complete boilerplate 👀