[sentry-junior]

Each enum-valued query parameter now gets a named type for one of its values, called <Operation>Query<Parameter>. For array parameters, it's the element type:

import type {
  ListOrganizationTraceItemAttributesQueryAttributeType, // "array" | "boolean" | "number" | "string"
  ListOrganizationTraceItemAttributesQueryDataset,       // "logs" | "preprod" | "processing_errors" | "spans" | "tracemetrics"
} from "@sentry/api";

The spec is dereferenced, so the generator inlines these enums in each operation's <Operation>Data type. Consumers currently have to dig them out by hand. getsentry/toolkit#1559 does exactly that:

type TraceItemAttributeValueType = NonNullable<
  NonNullable<ListOrganizationTraceItemAttributesData["query"]>["attributeType"]
>[number];

With these types, consumers import the name instead and no longer redeclare the shape themselves.

How it works

• scripts/generate-query-enum-types.mjs runs after generate-error-results.mjs. It maps each sdk.gen.ts operation to its route the same way that script does, and writes src/query-enums.gen.ts.
• Each alias derives from the existing <Operation>Data type rather than copying the enum values, so it can't drift from what the operation accepts.
• The root entry adds export type * from './query-enums.gen.ts'. It's type-only, so the bundle doesn't change.
• The build fails if an alias collides with an existing types.gen.ts export or with another alias. The Query infix keeps the names clear of the generator's Data, Error(s) and Response(s) suffixes.

The current spec produces 64 aliases across 36 operations. test/typecheck.ts checks a valid and an invalid dataset, and that the array parameter's alias is the element type. The README gains a short "Query parameter types" section.

Ran bun run build, bun run typecheck, bun test (163 pass) and bun run test:node.

via BYK.

--

View Junior Session in Sentry