gem-hunter
Language: TypeScript
PocketBase hook for automatically generating TypeScript interfaces and Zod schemas
PocketBase hook for automatically generating schemas for Zod and pocketbase-ts.
pb_hooks.zip from releases and extract it to the same directory as your PocketBase executable.config.json if necessary.exposeEndpoint set to true, you can access the generated schema through the endpoint you specified in endpointPath (e.g. https://URL_TO_YOUR_PB_SERVER/schema).The generated schema will have field options in docstrings, so you will get additional information like required, min, and max when you hover over properties in your IDE.
The config.json file should follow the structure below. (JSON schema is also provided in schema.json for validation purposes.)
interface Config { /** Whether to register the HTTP endpoint that serves the generated schemas. */ exposeEndpoint: boolean /** Path at which the schema endpoint will be exposed (e.g. \"/schema\"). Required if `exposeEndpoint` is set to `true`. */ endpointPath?: string /** Whether the schema endpoint should require authentication. Required if `exposeEndpoint` is set to `true`. */ secureEndpoint?: boolean /** Options controlling generation of the TypeScript schema file. */ tsSchema: BaseSchemaConfig & { /** Whether to include JSDoc comments with field metadata in the generated schema. */ includeDocs: boolean } /** Options controlling generation of the Zod schema file. */ zodSchema: BaseSchemaConfig } interface BaseSchemaConfig { /** Whether to generate and write the schema file to disk. */ generateFile: boolean /** Whether to include system collections like _superusers and _otps when generating the schema. */ includeSystemCollections: boolean /** File path where the generated schema will be written. Also used for the default filename when downloading from web UI. Required if `generateFile` is set to `true` */ outputPath?: string /** Array of strings to insert at the top of the generated schema file. Use this to import custom schema for overrides. */ banner?: string[] /** Specify the shape of JSON fields here. */ overrides?: { /** Names of collections with JSON fields. */ [collectionName: string]: { /** Name of the JSON field as key, and the shape of JSON as value. */ [fieldName: string]: string } } }
JSON fields are typed as any by default.
You can override this by specifying the type in the overrides object in your configuration file.
For example, if you have a collection called users with a JSON field called profile, you can specify the type like this:
// config.json { // ... "tsSchema": { // ... "overrides": { "users": { "profile": "{ name: string; age: number }", }, }, }, // ... }
Or for more complex types, you can define them in a separate file and reference them:
// jsonSchema.ts export interface UserProfile { name: string age: number }
// config.json { // ... "tsSchema": { // ... "overrides": { "users": { "profile": "import('./jsonSchema.ts').UserProfile", }, }, }, // ... }
or
// config.json { // ... "tsSchema": { // ... // specify import statements that need to be added to the top of the generated file "banner": ["import type { UserProfile } from './jsonSchema.ts'"], "overrides": { "users": { "profile": "UserProfile", }, }, }, }
This also applies to view collection fields.
If you have a view collection and some fields are typed as any, it is because PocketBase treats them as JSON fields.
You can override them the same way as above.
JSON fields are z.unknown() by default.
You can override this just like above.
// config.json { // ... "zodSchema": { // ... "overrides": { "users": { "profile": "z.object({ name: z.string(), age: z.number() })", }, }, }, }
// jsonSchema.ts export const userProfileSchema = z.object({ name: z.string(), age: z.number(), })
// config.json { // ... "zodSchema": { // ... "banner": ["import { userProfileSchema } from './jsonSchema.ts'"], "overrides": { "users": { "profile": "userProfileSchema", }, }, }, }