idea: allowing the `query` and `options` args to be reactive.

[trusktr]

For example,

const [query, setQuery] = createSignal(makeQuery(...args))
const data = createQuery(query, options)

createEffect(() => {
  console.log(data())
})

// later
// disposes the previous query internally, makes a new one with the new query document.
// the effect will re-run with the new result eventually
setQuery(makeQuery(...otherArgs)) 

One reason for this is I find it too cumbersome to write query variables. So this is much easier in various cases:

function makeQuery(foo: string, bar: string) {
  return gql`
    query SomeQuery {
      someStuff("${foo}", ${bar}) {
        foo
      }
    }
  `
}

[wiredmatt]

isn't it better to make the query use a signal?

const data = createQuery(`
  someStuff($foo, $bar) {
        foo
      }
    }
`, { 
      variables: {
          foo: foo(), 
          bar: bar() 
      }
   }
)

[trusktr]

Written that way it is less ergonomic.

The desired effect can be achieve with a memo wrapper actually (although it requires double calling):

const [query, setQuery] = createSignal(makeQuery(...args))
const [options, setOptions] = createSignal(initialOptions)
const data = createMemo(() => createQuery(query(), options()))

createEffect(() => {
  console.log(data()()) // double call
})

// later
// disposes the previous query, makes a new one with the new query.
// the effect will re-run with the new result eventually
setQuery(makeQuery(...otherArgs))