Setup clerk auth with middleware #116
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #12
📌 Description
Briefly explain what you implemented in this PR.
This PR sets up authentication on the frontend using Clerk with Next.js App Router. It ensures users can sign in and sign up, and protects private routes like the dashboard using middleware (no UI level checks)
🧩 Issue Reference
Related Issue: #12
🛠️ What Did You Implement?
Please list the major things you worked on in this PR:
(Select all that apply)
📁 Workspace Confirmation (MANDATORY)
Since all issues are Open for All, confirm the following:
contributors/<your-github-username>/client/and/orserver/files were copied from the main directory🧪 Testing Performed
Please check what applies:
📷 Screenshots / Demo (REQUIRED for most PRs)
verified locally
✅ Final PR Checklist
Before submitting, ensure:
.envfiles committed📎 Additional Notes for Reviewers
Authentication is enforced using Clerk middleware. UI components do not contain any auth logic