[Feature Request] `enabled` option should be reactive by default

[ylc395]

Now, If we want to update a Query's options, we should wrap the "dynamic options" in an option function like this:

const query = new MobxQuery({
  options: () => ({
    enabled: this.myObservableValue > 10,
  }),
});

Considering enabled is one of the mostly used options, we can make it reactive by default like:

const query = new MobxQuery({
    enabled: () => this.myObservableValue > 10,  //  which is a shortcut for `computed(() => this.myObservableValue > 10)`,
});

And queryFn should be able to be a computed too. like this:

const id = observable.box(null);

new MobxQuery({
    queryFn: computed(() => id.get() ? axios.get(`/api/id/${id.get()}`) : skipToken), // is a shortcut for `{ options: () => ({ queryFn: id.get() ? axios.get('/api/id/${id.get()}') : skipToken })}`, which is not supported now, too
})

All these cases can be found in official vue adapter document(considering vue-reactivity and mobx is almost the same thing, this library and official vue adaptor can share the same use cases and API design and even implementation):
https://tanstack.com/query/v5/docs/framework/vue/guides/disabling-queries

If you think these proposals are acceptable, I can submit a PR maybe this weekend?

[js2me]

If we will create enabled property with mobx "reactive" like this

const query = new MobxQuery({
    enabled: () => this.myObservableValue > 10,  //  which is a shortcut for `computed(() => this.myObservableValue > 10)`,
});

Then how we can use the default "out of box" functionality? I mean this construction

 enabled: (query: Query) => boolean

[ylc395]

You are right, so enabled: () => this.myObservableValue > 10 shouldn't be treated as a shortcut for enabled: computed(() => this.myObservableValue).

So, in MobxQuery constructor, if enabled is a function, we just call it with Query instance in a reaction or autorun, if it's a computed, we just call it's get() function in a reaction or autorun?