defineQuery in composables with parameters

[niklaswolf]

Is it necessary to use defineQuery in the following case, or is it sufficiant to use useQuery?
How would I use defineQuery in such a case, because the setup function doesn't allow for parameters.

// outside
const todoId = ref('my-id')
const {data} = useTodo(todoId)

// composable to group all functionality for a single todo
const useTodo = (id: Ref<string>) => {
    const query = useQuery({
        key: () => ['todo', id.value],
        query: () => {
            return fetch(`/api/todos/${id}`)
        }
    })

    // other function regarding a todo, e.g. a mutation
    const otherFunction = () => {...}

    return {...query, otherFunction}
}

The useTodo composable would be reused in multiple places.

[posva]

In this case of scenario, the todoId would be inside of the defineQuery():

// composable to group all functionality for a single todo
const useTodo = defineQuery(() => {
  const id = ref('my-id')
  const query = useQuery({
    key: () => ['todo', id.value],
    query: () => {
      return fetch(`/api/todos/${id}`)
    },
  })

  // other function regarding a todo, e.g. a mutation
  const otherFunction = () => {}

  return { ...query, otherFunction, id }
})

This makes id a global ref though. Where is this id coming from? Usually I would put this kind of information in the route, allowing me to use it within defineQuery too

[ralacerda]

Is it the same as a Pinia Setup Store where you are required to return all refs?

[posva]

no, this one is different, it's closer to a composable