14e3ab125b
Error statuses follow one rule: APIException takes a status and derives the code from it (BAD_REQUEST 400, UNAUTHORIZED 401, FORBIDDEN 403, NOT_FOUND 404, CONFLICT 409, RATE_LIMITED 429, SERVER_ERROR 500, BAD_GATEWAY 502), so a code can't contradict its status. That fixed real bugs: a wrong current password on change-password answered 401, on which authFetch signs the user out; editing or deleting someone else's comment or chat message answered 401 rather than 403; one invalid dump edit answered 422. A taken username is 409, like a taken email. Along the way: the database is created from schema.sql by connection.ts when the file doesn't exist, so every task works on a fresh checkout (dev and serve never ran db/init.ts, which is gone); the startup purge compared ISO dates with SQLite's datetime() as text and kept anything from the current UTC day, and now compares ISO cutoffs; the seeded admin's hash comes from lib/password.ts (split out of jwt.ts, which needs the JWT secret) rather than a copy of its format; avatar, thumbnail and playlist-cover uploads go through replaceUploadedFile, which writes beside the old file and renames over it before the record announces it (a failed avatar write lost the old avatar; a thumbnail was announced before it existed); upload.ts derives its size message from MAX_IMAGE_SIZE_BYTES and stops re-exporting the upload folders; ALLOWED_IMAGE_MIMES, which duplicated detectImageMime, is gone; the SPA fallback no longer calls next() after answering; a reply must answer a comment on the same dump (a foreign or unknown parent was a 500 or a cross-dump thread). 211 backend and 628 frontend tests pass. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
49 lines
1.7 KiB
TypeScript
49 lines
1.7 KiB
TypeScript
/**
|
|
* Serves the invite endpoints. Any signed-in user can invite someone, from
|
|
* their profile page, and the invite link opens the `/register` page.
|
|
*
|
|
* - `POST /api/invites` — signed in. Makes an invite and answers its token.
|
|
* - `GET /api/invites/:token` — public. Checks that an invite still works,
|
|
* before the register page shows its form; 404 when it doesn't.
|
|
*
|
|
* @module
|
|
*/
|
|
|
|
import { Router } from "@oak/oak";
|
|
import { type APIResponse } from "../../shared/api.ts";
|
|
import { APIException } from "../lib/api-exception.ts";
|
|
import type { InviteResponse } from "../../shared/user.ts";
|
|
import { type AuthContext, authMiddleware } from "../middleware/auth.ts";
|
|
import { createInvite, validateInvite } from "../services/invite-service.ts";
|
|
|
|
/**
|
|
* Mounted by `api/main.ts` behind the error, Open Graph and CORS middleware.
|
|
* An `APIException` thrown by a handler becomes the JSON error response there.
|
|
*/
|
|
const router: Router = new Router({ prefix: "/api/invites" });
|
|
|
|
router.post("/", authMiddleware, (ctx: AuthContext) => {
|
|
if (!ctx.state.user) {
|
|
throw new APIException(401, "Not authenticated");
|
|
}
|
|
const responseBody: APIResponse<InviteResponse> = {
|
|
success: true,
|
|
data: { token: createInvite(ctx.state.user.userId) },
|
|
};
|
|
ctx.response.status = 201;
|
|
ctx.response.body = responseBody;
|
|
});
|
|
|
|
router.get("/:token", (ctx) => {
|
|
// A used invite answers 404 too: the page only needs to know it won't work.
|
|
try {
|
|
validateInvite(ctx.params.token);
|
|
const responseBody: APIResponse<null> = { success: true, data: null };
|
|
ctx.response.body = responseBody;
|
|
} catch {
|
|
throw new APIException(404, "Invalid or expired invite");
|
|
}
|
|
});
|
|
|
|
export default router;
|