Repository navigation
Feature/authentication/phase2 - #66
Conversation
017f071 to
b4b759c
Compare
|
Phase 2 complete Implemented the frontend authentication flow, GitHub storage picker, storage validation/setup, real user state, logout flow, and replaced placeholder data with backend-powered APIs. Google support remains deferred to Phase 3. |
ieliofficial
left a comment
There was a problem hiding this comment.
Good progress here, especially the provider-neutral frontend flow and the added tests. I found three issues that need fixing before merge:
- Please verify the signed-in user can access the submitted repo, and that its GitHub node ID matches
storageRef.id, before minting an installation token. Right now a user could submit another repo where the app is installed. - Please make concurrent scan saves merge against current scan truth. Refreshing only the SHA can overwrite a newer index, and the three sequential writes can leave partial state. A two-writer test would help confirm the fix.
- Please open saved reports by scan ID from storage. The current dashboard click starts a fresh scan of the host, so it does not show the saved historical report.
The backend suite and frontend build pass. Once these data access and persistence issues are addressed, this will be in much better shape.
Wire GitHub connect/load/init, installation-token writes with repo access checks, concurrent scan-save merge against storage truth, and open saved reports by scan id from the dashboard. Co-authored-by: Cursor <cursoragent@cursor.com>
bc3ad18 to
0e52dc0
Compare
|
Good progress. The saved-report-by-id flow works, the repo access check is in, and the concurrent-save reconcile is a real step up. Two things still block merge:
Also get lint green before the next push (set-state-in-effect in App.jsx, and the |
ieliofficial
left a comment
There was a problem hiding this comment.
All three issues are sorted. 🎉
Phase 2: Frontend — Auth + GitHub Connect
Provider-neutral API shape; GitHub picker wired, Google deferred to Phase 3.