next-learn

Before submitting [x] I have searched existing issues to make sure this isn't a duplicate [x] I have completed this chapter and encountered the issue myself Chapter URL https://nextjs.org/learn/dashboard-app Issue Type Other Description When logged in to the Next.js Learn Dashboard, chapter completion indicators from one course are temporarily shown in another course. Steps to reproduce 1. Log in to Next.js Learn. 2. Complete several chapters in the App Router course (e.g. 10 chapters). 3. Open the course switcher. 4. Select another course, such as SEO. 5. Observe that the first N chapters (where N is the number of completed App Router chapters) are displayed with completion checkmarks. The issue appears to be visual only. Clicking into a chapter in the second course causes the completion state to refresh and the incorrect checkmarks disappear. Expected vs Actual Behavior Expected: Only chapters that have been completed in the selected course should display completion checkmarks. Actual: The course switcher initially displays completion checkmarks carried over from another course. After navigating to a chapter in the selected course, the UI refreshes and the completion indicators are corrected. Environment (optional) OS: macOS Browser: Chrome 149.0.7827.115 (Official Build) (arm64) Logged-in user: Yes Screenshots (optional)

Hi Next.js team 👋 While following the Next.js App Router tutorial and implementing the file, I noticed a few issues in the seed script that can cause confusion or subtle bugs for learners. I wanted to document them here in case it’s helpful to improve the tutorial. Below is a summary of the findings and suggested fixes. Issues identified 1. Transaction is not actually used The seed script uses: However, the functions use the outer client, not the transactional client passed into . As a result, the queries do not run inside the transaction, despite appearing to do so. Suggested fix Pass the transaction client into each seed function and use that client for queries. 2. used without inserting (invoices) In the invoices seed: Since is auto-generated and never inserted, this conflict clause will never trigger and is effectively a no-op. Suggested fix Remove the clause 3. Missing foreign key constraint on The invoices table defines: but does not reference the table. This allows invoices to exist without a valid customer. Suggested fix This aligns with how invoices are queried later in the tutorial. 4. Repeated calls is executed in multiple seed functions. Extensions are database-wide, so this is redundant (though harmless). Suggested fix** Run the extension creation once before the transaction begins. Other than that, thanks for the excellent tutorial content overall, it’s been a great learning experience!