Discover and read the best of Twitter Threads about #sideEffectFreeFunctions
Most recents (1)
the fact that you can write/mutate and read/query from the same call or transaction in #graphql.
powerful flexibility or anti pattern?
powerful flexibility or anti pattern?
by same call i mean same transaction, same request response cycle
i think im seeing it right?
you can mutate/write, and fetch what was mutated/written in the same round trip. OK
but you can't query/read, and then mutate/write anything "on the side", which would violate side-effect free functions, and idempotence. OK again
you can mutate/write, and fetch what was mutated/written in the same round trip. OK
but you can't query/read, and then mutate/write anything "on the side", which would violate side-effect free functions, and idempotence. OK again
