help: Some problem with useFetch about composition-api HOT 4 CLOSED

Really cool! It works well! Thank you! 🎉! You can close this issue now!

from composition-api.

@namadnuno Thanks for the report and kind words 😃

The warning is not something to worry about, although suggestions/help are welcome as far as getting rid of it. (I've created #19 to track.)

As far as the mismatch is concerned, fetch() in Nuxt 2.12+ only looks after the component state (which in this context is what is returned from setup()). So this would work:

{
  setup() {
    const post = ref(null)

    async function loadPost() {
      ...
    }

    useFetch(async () => {
      await loadPost();
    })

    return { post }
  }
}

For improved composability (given that a lot of state is stored off-component with the Composition API), I plan to create a ssrRef function that will automatically stringify and rehydrate refs on client-side, independent of component context. #20

from composition-api.

Thanks a lot for answering 👍, I will keep it into consideration, and will wait until those are implemented!

from composition-api.

@namadnuno Fingers crossed, if you use ssrRef for your state, everything should now work. I'll wait to hear back before closing the issue though.

from composition-api.