mirror of
https://github.com/screentinker/screentinker.git
synced 2026-08-14 06:16:20 -06:00
6dd78e078a
optionalAuth was exported but never mounted on any route (verified by grep across server, frontend, scripts and tests: only its own definition, its export, and one stale comment referenced it). It also carried a second, slightly different copy of the token-resolution logic - its own user column list, and no forced-password-change check - which is exactly the drift the preceding commit consolidates away. Removing it rather than porting it to resolveSessionUser: a "set req.user if a token happens to be present" middleware is a few lines on top of the shared resolver if a route ever needs one, and an unused export is a standing invitation to mount it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| apiToken.js | ||
| auth.js | ||
| sanitize.js | ||
| subscription.js | ||
| upload.js | ||