default.tsx parallel routes are using the loading.tsx from the parent route instead of the one from the parallel route about next.js HOT 1 OPEN

I know I could add a suspense boundary to wrap the header on the layout.tsx file for example, but then I can't access searchParams on layout.tsx, so it must be a page.tsx in a parallel route... Does anyone know a way around this? Hopefully it's gonna be fixed and the default pages will show the loading state from the parallel route instead of the loading state from the parent main route.

Edit: A way around this would be to wrap the content inside the @header and @sidebar parallel routes with the suspense, but then, I don't see why not allow having the loading.tsx page to show the loading state.

from next.js.