fix: [Vue warn]: Write operation failed: computed value is readonly.

🐛 The bug At the moment, if a component that calls useFetch has a computed property returned from setup, it will give the following error:

[Vue warn]: Computed property was assigned to but it has no setter.

It still works correctly, but this is unattractive, and ideally we wouldn’t be attempting to assign a value to a computed property at all.

[danielroe]

@chovyprognos In the composition API you would do that like so:

const a = computed({
  get() {
    // your getter
  },
  set(val) {
    // your setter
  }
})

[sethidden]

@davaipoka Hm, you’re right. I had a computed that depended on two values (say countries and user addresses). The client-side render worked but the server-side didn’t work (computed value was not pre-populated). When I added the dependencies the computed relies on - countries and user addresses refs to the setup function’s return object, the server-side render started working.

Normally I wouldn’t include those 2 refs in the return object - they’re not used in the template. But if it makes it work it makes it work.