[NextJS] Use web frameworks' built-in auth cookie instead of custom implementation

Open
#243 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
firebase, javascript, nextjs
Domain
authentication, backend

Research direction

Compare the Firebase CLI framework cookie setup in src/firebase-aware.ts with the custom implementation in nextjs-end/src/app/api/route.js. Trace how the Next.js API route currently handles authentication, then verify that it uses the web framework's built-in auth cookie instead of maintaining the custom implementation.

Written by the indexing model from the issue text.

Description

The Firebase CLI's web frameworks tooling sets an auth cookie: https://github.com/FirebaseExtended/firebase-framework-tools/blob/087035d86c65c5810ab71f889e4d6160398368aa/src/firebase-aware.ts#L32

This means we probably don't need the current custom implementation: https://github.com/firebase/friendlyeats-web/blob/c43de974fbf44151217fe3238d610edee7b86b28/nextjs-end/src/app/api/route.js#L9

Dominant language
JavaScript
Stars
597
Forks
456
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/friendlyeats-web

All issues in firebase/friendlyeats-web

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.