I have what might be a stupid question... Is there a mutation that increments an integer field, instead of setting it directly?

@morley AFAIK you can only do this in the TRANSFORM_ARGUMENT hook. See https://github.com/graphcool/feature-requests/issues/122 for a possibly related feature request.

Hmm. I'm not sure TRANSFORM_ARGUMENT works for me. I want to increment the existing value, not manipulate the value that I'm getting in from the server.

What would trigger that function?

This is a ticket that asks about what I'm trying to do: https://stackoverflow.com/questions/43087914/howto-increment-the-value-of-an-integer-based-field-in-graphql

Is https://stackoverflow.com/questions/43087914/howto-increment-the-value-of-an-integer-based-field-in-graphql#comment73525705_43096141 still your only issue with it?

With the client-side option? Yeah, that summarizes it

You could cheat by raising an error in the pre_write event hook for the Vote table. That way, you can update your likes based on the payload of the Vote type, but prevent the creation of the actual record.

Making a new table seems better for my use case

_votesMeta { count }

cool thanks!

But with my approach, you wouldn't have an entry in a new table for every single like...

Hmm... I see what you're saying but I think it's better to worry about scaling later

True

Yup!

Updated my count answer, made a typo... it's _votesMeta, not _votesMetadata

👍

Really interesting discussion, I like @agartha's suggestion a lot. Would love to hear back from you @morley if you run into any problems with this approach 🙂