mirror of
https://github.com/ajnart/homarr.git
synced 2026-01-30 19:29:17 +01:00
* refactor: move zod import from validation package to zod * refactor: move missing zod imports
161 lines
4.7 KiB
TypeScript
161 lines
4.7 KiB
TypeScript
/**
|
|
* YOU PROBABLY DON'T NEED TO EDIT THIS FILE, UNLESS:
|
|
* 1. You want to modify request context (see Part 1)
|
|
* 2. You want to create a new middleware or type of procedure (see Part 3)
|
|
*
|
|
* tl;dr - this is where all the tRPC server stuff is created and plugged in.
|
|
* The pieces you will need to use are documented accordingly near the end
|
|
*/
|
|
import { initTRPC, TRPCError } from "@trpc/server";
|
|
import superjson from "superjson";
|
|
import type { OpenApiMeta } from "trpc-to-openapi";
|
|
import { ZodError } from "zod";
|
|
|
|
import type { Session } from "@homarr/auth";
|
|
import { FlattenError } from "@homarr/common";
|
|
import { userAgent } from "@homarr/common/server";
|
|
import { db } from "@homarr/db";
|
|
import type { GroupPermissionKey, OnboardingStep } from "@homarr/definitions";
|
|
import { logger } from "@homarr/log";
|
|
|
|
import { getOnboardingOrFallbackAsync } from "./router/onboard/onboard-queries";
|
|
|
|
/**
|
|
* 1. CONTEXT
|
|
*
|
|
* This section defines the "contexts" that are available in the backend API.
|
|
*
|
|
* These allow you to access things when processing a request, like the database, the session, etc.
|
|
*
|
|
* This helper generates the "internals" for a tRPC context. The API handler and RSC clients each
|
|
* wrap this and provides the required context.
|
|
*
|
|
* @see https://trpc.io/docs/server/context
|
|
*/
|
|
export const createTRPCContext = (opts: { headers: Headers; session: Session | null }) => {
|
|
const session = opts.session;
|
|
const source = opts.headers.get("x-trpc-source") ?? "unknown";
|
|
|
|
logger.info(`tRPC request from ${source} by user '${session?.user.name} (${session?.user.id})'`, session?.user);
|
|
|
|
return {
|
|
session,
|
|
deviceType: userAgent(opts.headers).device.type,
|
|
db,
|
|
};
|
|
};
|
|
|
|
/**
|
|
* 2. INITIALIZATION
|
|
*
|
|
* This is where the trpc api is initialized, connecting the context and
|
|
* transformer
|
|
*/
|
|
const t = initTRPC
|
|
.context<typeof createTRPCContext>()
|
|
.meta<OpenApiMeta>()
|
|
.create({
|
|
transformer: superjson,
|
|
errorFormatter: ({ shape, error }) => ({
|
|
...shape,
|
|
data: {
|
|
...shape.data,
|
|
zodError: error.cause instanceof ZodError ? error.cause.flatten() : null,
|
|
error: error.cause instanceof FlattenError ? error.cause.flatten() : null,
|
|
},
|
|
}),
|
|
});
|
|
|
|
/**
|
|
* Create a server-side caller
|
|
* @see https://trpc.io/docs/server/server-side-calls
|
|
*/
|
|
export const createCallerFactory = t.createCallerFactory;
|
|
|
|
/**
|
|
* 3. ROUTER & PROCEDURE (THE IMPORTANT BIT)
|
|
*
|
|
* These are the pieces you use to build your tRPC API. You should import these
|
|
* a lot in the /src/server/api/routers folder
|
|
*/
|
|
|
|
/**
|
|
* This is how you create new routers and subrouters in your tRPC API
|
|
* @see https://trpc.io/docs/router
|
|
*/
|
|
export const createTRPCRouter = t.router;
|
|
|
|
/**
|
|
* Public (unauthed) procedure
|
|
*
|
|
* This is the base piece you use to build new queries and mutations on your
|
|
* tRPC API. It does not guarantee that a user querying is authorized, but you
|
|
* can still access user session data if they are logged in
|
|
*/
|
|
export const publicProcedure = t.procedure;
|
|
|
|
/**
|
|
* Reusable middleware that enforces users are logged in before running the
|
|
* procedure
|
|
*/
|
|
const enforceUserIsAuthed = t.middleware(({ ctx, next }) => {
|
|
if (!ctx.session?.user) {
|
|
throw new TRPCError({ code: "UNAUTHORIZED" });
|
|
}
|
|
return next({
|
|
ctx: {
|
|
// infers the `session` as non-nullable
|
|
session: { ...ctx.session, user: ctx.session.user },
|
|
},
|
|
});
|
|
});
|
|
|
|
/**
|
|
* Protected (authed) procedure
|
|
*
|
|
* If you want a query or mutation to ONLY be accessible to logged in users, use
|
|
* this. It verifies the session is valid and guarantees ctx.session.user is not
|
|
* null
|
|
*
|
|
* @see https://trpc.io/docs/procedures
|
|
*/
|
|
export const protectedProcedure = t.procedure.use(enforceUserIsAuthed);
|
|
|
|
/**
|
|
* Procedure that requires a specific permission
|
|
*
|
|
* If you want a query or mutation to ONLY be accessible to users with a specific permission, use
|
|
* this. It verifies that the user has the required permission
|
|
*
|
|
* @see https://trpc.io/docs/procedures
|
|
*/
|
|
export const permissionRequiredProcedure = {
|
|
requiresPermission: (permission: GroupPermissionKey) => {
|
|
return protectedProcedure.use(({ ctx, input, next }) => {
|
|
if (!ctx.session.user.permissions.includes(permission)) {
|
|
throw new TRPCError({
|
|
code: "FORBIDDEN",
|
|
message: "Permission denied",
|
|
});
|
|
}
|
|
return next({ input, ctx });
|
|
});
|
|
},
|
|
};
|
|
|
|
export const onboardingProcedure = {
|
|
requiresStep: (step: OnboardingStep) => {
|
|
return publicProcedure.use(async ({ ctx, input, next }) => {
|
|
const currentStep = await getOnboardingOrFallbackAsync(ctx.db).then(({ current }) => current);
|
|
if (currentStep !== step) {
|
|
throw new TRPCError({
|
|
code: "FORBIDDEN",
|
|
message: "Step denied",
|
|
});
|
|
}
|
|
|
|
return next({ input, ctx });
|
|
});
|
|
},
|
|
};
|