Trigger another request if the variables or query change

[jackdclark]

The issue

See #35

The following tests are failing because there should be a second request that currently isn't being sent

✕ sends the query again if the variables change, even if there was previously data (3ms)
✕ sends the query again if the variables change, even if there was previously an error (3ms)
✕ sends the query again if the query changes, even if there was previously data (2ms)
✕ sends the query again if the query changes, even if there was previously an error (2ms)

The fix

Remove the state.data & state.error check inside the useQuery effect. It already has conditional checks to make sure it only fires if query or opts.variables have changed.

✓ sends the query again if the variables change, even if there was previously data (3ms)
✓ sends the query again if the variables change, even if there was previously an error (2ms)
✓ sends the query again if the query changes, even if there was previously data (2ms)
✓ sends the query again if the query changes, even if there was previously an error (2ms)

[Joezo]

Just tried this branch out in the example app and it worked well 🎉