Update "API Routes" to "Route Handlers" in Next.js App Router documentation
Description
This PR updates the terminology in the Next.js App Router documentation from "API Routes" to "Route Handlers". This change aligns the documentation with the current Next.js terminology, improving clarity and consistency for users implementing authentication with the App Router.
Changes
Updated the following files:
nextjs-app.md (Validate session cookies guide)
nextjs-app.md (GitHub OAuth guide)
nextjs-app.md (Username and password auth guide)
Replaced all instances of "API Routes" with "Route Handlers"
Example of changes
Before:
Create an API routes in `app/login/github/route.ts`.
After:
Create a Route Handlers in `app/login/github/route.ts`.
Motivation
The current documentation uses outdated terminology from the Pages Router, which may confuse users implementing authentication with the newer App Router. This update ensures the documentation accurately reflects the current Next.js best practices.
Additional Notes
This is a minor terminology update and does not change any functionality or code examples.
The changes are limited in scope, focusing only on updating the "API Routes" terminology.
File paths and other content remain unchanged.
I believe this small change aligns with the project's goals of maintaining simplicity and clarity in the documentation. If any adjustments are needed or if you'd prefer a different approach, please let me know.
Update "API Routes" to "Route Handlers" in Next.js App Router documentation
Description
This PR updates the terminology in the Next.js App Router documentation from "API Routes" to "Route Handlers". This change aligns the documentation with the current Next.js terminology, improving clarity and consistency for users implementing authentication with the App Router.
Changes
nextjs-app.md
(Validate session cookies guide)nextjs-app.md
(GitHub OAuth guide)nextjs-app.md
(Username and password auth guide)Example of changes
Before:
After:
Motivation
The current documentation uses outdated terminology from the Pages Router, which may confuse users implementing authentication with the newer App Router. This update ensures the documentation accurately reflects the current Next.js best practices.
Additional Notes
I believe this small change aligns with the project's goals of maintaining simplicity and clarity in the documentation. If any adjustments are needed or if you'd prefer a different approach, please let me know.