chaithanya

> Thanks for the catch, I think it's better to get the user info in `user-nav.tsx` rather than in navbar.tsx to avoid the prop drilling because `navbar.tsx` does not use...

> > > Thanks for the catch, I think it's better to get the user info in `user-nav.tsx` rather than in navbar.tsx to avoid the prop drilling because `navbar.tsx` does...

The current approach is better than calling it in the user-nav for mainly two reasons: 1. useEffects are not compatible with Suspense since it happens after page mount, so we...

> > The current approach is better than calling it in the user-nav for mainly two reasons: > > > > 1. useEffects are not compatible with Suspense since it...

> 1. Content Layout shouldn't exist. In NextJS apps, the Layout component is responsible for these layouts that are repeated across the app. > 2. The user should be requested...

Hi @alejandrobailo . Implemented the long term fix! Objective: Centralize page layout management by moving title/icon definitions and navbar functionality from individual pages into the main layout component. What Changed:...

hi @wellhrd . You need to add a /health endpoint in the UI and point the load balancer to it. // ui/app/api/health/route.ts ` import { NextResponse } from "next/server"; export...