Is it an ok usage pattern to do api calls inside the beforeload of a route?

[mkarajohn]

There are some scenarios where we need to know beforehand the state of some server data before we can even render the page to the user; we may need to redirect them somewhere else based on what that data is. Or, for example, in order to show a specific item's title as part of the breadcrumbs, we need that server information in order to include it in the breadcrumb context we return in the beforeLoad

I want to make sure there are no gotchas or some better way to do it

inversely, is it ok to throw a redirect inside the loader function instead of the beforeLoad function ?

[schiller-manuel]

both is "ok". you can call an API in beforeLoad and you can also throw a redirect in a loader.

you just need to understand the consequences:

when you navigate to /foo/bar/baz, this would for example match 3 nested routes (foo, bar, baz), then following happens:

1. beforeLoad of all those routes run serially, so first foo's beforeLoad, then bar's beforeLoad, baz's beforeLoad
2. loader of all those routes run in parallel. so if one loader throws a redirect, the other loaders would still execute!

[mkarajohn]

Thanks!