Nuxt•3y ago

useFetch adds null to return type

When using

useFetch

useFetch

to fetch data from server api routes,

useFetch

useFetch

adds

null

null

as a union to the return type.
Because I use typescript strict mode, this forces me to do null checks to api routes which already handle this.
If I understand correctly, when using SSR,

useFetch

useFetch

is just an async function call to the api endpoints?
Then why does it add null to the type?

If this works as intended, how would I check if the data is null inside

script setup

script setup

script setup

script setup

GerbuuunOP•12/26/22, 3:34 PM

A similar problem goes for returning a DateDate. It becomes a

string

string

(because jsonjson doesn't support DateDate?)
But typescript still thinks it is a DateDate which is quite annoying.
Are these known issues? Maybe add some transform into the

useFetch

useFetch

composable?

GerbuuunOP•12/27/22, 6:46 PM

The return type changes from Ref<regattas[] | null>Ref<regattas[] | null> to Ref<SerializeObject<UndefinedToOptional<regattas[]>> | null>Ref<SerializeObject<UndefinedToOptional<regattas[]>> | null> so something still adds

null

null

to the type.

GerbuuunOP•12/27/22, 9:02 PM

Ok, I thought when using SSR this wouldn't be a problem. So how would I check the data for

null

null

? The example given at the top doesn't do anything. Do I need to wrap it in a computedcomputed or anything?

useFetch adds null to return type

Similar Threads

Similar Threads

Similar Threads