breaking change on swapping composables

[derrickobedgiu1]

Hey @manchenkoff , I see PR #475 swapped useAsyncData to useFetch . This is going to be a lot of work to do on developer end because those who used the composable including me were intentionally after the nuxt cache and would use the sanctum client composable for live data. Little has been provided on the upgrade process besides now looking for the composable that does the api call cache. It's a bit hard to jump to v2 given these constraints, and I think it'd be really great if we got early communication on these sort of changes which would have helped prevent heavy reliance on the composable that's really changed trajectory greatly.

I'd also like to know if the useSanctumClient is still applicable given the swap of the composable.

[manchenkoff]

Hey @derrickobedgiu1

This is going to be a lot of work to do on developer end because those who used the composable including me were intentionally after the nuxt cache and would use the sanctum client composable for live data.

It should not be a lot of work since useFetch uses useAsyncData under the hood anyway. For 99% of cases it will be just a drop-in replacement. Only in those cases, where you used 3/4 arguments calls of useSanctumFetch you would need to merge those arguments into a single options param. No need to refactor anything else.

Little has been provided on the upgrade process besides now looking for the composable that does the api call cache.

There is no upgrade process since the contract and functionality are still the same. The only breaking change here is that I removed a couple of arguments from useSanctumFetch which were separating client options and async data options. They are now defined as a single argument.

It's a bit hard to jump to v2 given these constraints, and I think it'd be really great if we got early communication on these sort of changes which would have helped prevent heavy reliance on the composable that's really changed trajectory greatly.

This is why it's been released as breaking change. You do not have to upgrade immediately. However, the functionality of composable hasn't changed. If you want to use Nuxt caching, it will work with useFetch as well.

I'd also like to know if the useSanctumClient is still applicable given the swap of the composable.

Not sure I understand this question. No changes to useSanctumClient has been made.