useAsyncData unexpected behaviour when callback return falsy value

[VladStepanov]

useAsyncData unexpected behaviour when callback return falsy value

[VladStepanov]

@danielroe thanks for clarification!
Maybe it's better to raise an exception or log a warning if undefined value returned? Because this behaviour is not obvious

[danielroe]

Agreed! We could log a warning in dev mode? I think we might also consider updating types to exclude false return values.

[danielroe]

Why are you not returning something from useAsyncData?

[VladStepanov]

Why are you not returning something from useAsyncData?

It is a liitle bit non documentation way.
Anyway this behaviour is unexpected

[danielroe]

This is documented:

You (I suspect) are relying on useAsyncData to dispatch a side-effect like calling a pinia action. I would advise against that. useAsyncData is not guaranteed to execute the function on transitioning to the page. It might be extracted at build/generate time, for example. Or perhaps run in advance before navigating to another page.