Component executed even though data function navigates, bug?

[adjourn]

Anyone else encountered the "issue" where route component still runs if data navigates?

For example this route:

<Route path="/example" component={Example} data={fetchExample} />

function fetchExample() {
  // I expected that data function bails out,
  // Example component is not executed,
  // route before navigating here is held active,
  // while /login starts "loading" in the background
  if (notLoggedIn()) return navigate('/login');

  const [user] = createResource(...);
  return { user: user };
}

function Example() {
  // ERROR: Cannot destructure property 'user' of as it is undefined
  const { user } = useRouteData();
  // ...
}

It looks like the navigation is started and return returns to component still.
For example if I changed the logic at the beginning of fetchExample to this:

if (notLoggedIn()) {
  navigate('/login');
  return {};
}

const { user } = useRouteData(); // "useRouteData" returns empty object now

This feels like a bug to me. It doesn't happen on every navigation to /example but sometimes.

I use Suspense and all routes are transitioned.
What do you think? Am I wrong and it's expected due to the "concurrent" nature of this?

If that's the case, what would you recommend to make it as pleasant and logical as possible?
Guard each data read? Run createResource even if navigate is called?

All these options don't make me too happy honestly.