[SQL Connect / Data Connect] adminNodeSdk TypeScript codegen references enum type names without declaring or exporting them in index.d.ts

[mafreud]

[REQUIRED] Environment info

firebase-tools: 15.15.0

Platform: macOS 25.4.0 (darwin)

Node.js version: v22.22.2

firebase-admin version: 13.x

TypeScript version: 5.5.x

[REQUIRED] Test case

Generate the Node Admin SDK (adminNodeSdk) for a connector whose schema
contains a user-defined enum that is selected by a query.

dataconnect/schema/schema.gql:

enum InvitationStatus {
  PENDING
  ACCEPTED
  EXPIRED
}

type Invitation @table(key: "id") {
  id: UUID! @default(expr: "uuidV4()")
  email: String! @index
  token: String! @col(dataType: "text") @unique
  status: InvitationStatus! @default(value: PENDING)
  expiresAt: Timestamp!
  createdAt: Timestamp! @default(expr: "request.time")
}

dataconnect/connector/queries.gql:

query GetInvitationByToken($token: String!) @auth(level: USER) {
  invitations(where: { token: { eq: $token } }, limit: 1) {
    id
    email
    status
    expiresAt
    createdAt
  }
}

dataconnect/connector/connector.yaml:

connectorId: default
generate:
  adminNodeSdk:
    outputDir: ../../ts_functions/src/generated/dataconnect
    package: "@example/dataconnect-admin"
    packageJsonDir: ../../ts_functions

[REQUIRED] Steps to reproduce

1. rm -rf ts_functions/src/generated/dataconnect
2. npx firebase-tools@15.15.0 dataconnect:sdk:generate
3. Open the generated ts_functions/src/generated/dataconnect/index.d.ts.
4. Search the file for InvitationStatus.

[REQUIRED] Expected behavior

The generated index.d.ts should declare and export a TypeScript type for
every user-defined enum referenced in a query selection set, similar to how
scalar aliases are emitted today. For example:

export type InvitationStatus = "PENDING" | "ACCEPTED" | "EXPIRED";

so that the enum name referenced inside generated *Data interfaces
resolves correctly and can be imported by user code.

[REQUIRED] Actual behavior

The generated index.d.ts references InvitationStatus but never
declares or exports it. The only occurrence in the whole file is the
following line inside the query's Data interface:

export interface GetInvitationByTokenData {
  invitations: ({
    id: UUIDString;
    email: string;
    status: InvitationStatus;   // <-- name is not defined anywhere
    expiresAt: TimestampString;
    createdAt: TimestampString;
    // ...
  } & Invitation_Key)[];
}

Header of the file (for context) shows scalar aliases are exported, but no
enum alias / union is emitted:

import { ConnectorConfig, DataConnect, OperationOptions, ExecuteOperationResponse } from 'firebase-admin/data-connect';

export const connectorConfig: ConnectorConfig;

export type TimestampString = string;
export type UUIDString = string;
export type Int64String = string;
export type DateString = string;
// <-- no `export type InvitationStatus = ...` anywhere

InvitationStatus is also not re-exported from
firebase-admin/data-connect, so any consumer importing the generated
module gets TS2304 (Cannot find name 'InvitationStatus') when the
field is actually referenced, and downstream code is forced to
redeclare the union by hand, duplicating the schema.

Notes:

• The Dart SDK generator does emit enum types from the same
  schema.gql in the same run, so the missing emission looks
  TypeScript-specific.
• This is distinct from Data Connect SDK generation with llmTools option does not support Enums #8929 (llmTools enum failure, already fixed)
  and [Data Connect] Admin SDK bulk insert/insertMany fails to serialize enum values correctly (GraphQL coercion error) #9650 (runtime serialization of enum values). Those issues do
  not cover the TypeScript type emission gap.

Minimal suggested fix

For every enum type that appears in any generated *Data interface
(or *Variables interface), emit a corresponding

export type <EnumName> = "<Value1>" | "<Value2>" | ...;

near the other exported type aliases (UUIDString, TimestampString,
etc.) at the top of index.d.ts, and emit the matching string-literal
values in index.cjs.js / esm/index.esm.js if a runtime object form
is also desired (otherwise the .d.ts alias alone is enough to resolve
the reference).

[aalej]

Hey @mafreud, thanks for the thorough report! I'm working on reproducing this but the generated SDK seems to declare InvitationStatus. Here's the generated index.d.ts file from my mcve - could you give this a try? if I am missing something here or misunderstood anything from the report, just let me know.

[mafreud]

@aalej Thank you! I will check ASAP.

[mafreud]

@aalej Thanks for the quick investigation! I tried reproducing with a clean setup:

1. Deleted ~/.cache/firebase/emulators/dataconnect-emulator-*
2. rm -rf ts_functions/src/generated/dataconnect
3. npx -y firebase-tools@latest dataconnect:sdk:generate --debug

The emulator was re-downloaded as dataconnect-emulator-3.4.5 (same version). The generated index.d.ts is 9847B and still only references InvitationStatus at line 91 inside GetInvitationByTokenData without declaring it.

I noticed your MCVE uses only adminNodeSdk in connector.yaml, while mine also has dartSdk alongside it:

connectorId: default
generate:
  dartSdk:
    outputDir: ../../../apps/dashboard/lib/generated/dataconnect
    package: openci_dataconnect
  adminNodeSdk:
    outputDir: ../../ts_functions/src/generated/dataconnect
    package: "@openci/dataconnect-admin"
    packageJsonDir: ../../ts_functions

Could having both dartSdk and adminNodeSdk in the same connector affect the codegen output? Or could the difference be in the emulator binary version used? Your MCVE's generated index.d.ts correctly includes export enum InvitationStatus { ... }, but mine does not.

Happy to provide any additional debug logs if needed.

[aalej]

Thanks @mafreud! Adding that dartSdk config did the trick. After adding that, the generated Admin SDK has a missing declaration for InvitationStatus. I've updated the MCVE. Will mark this as reproducible and raise this to our engineering team.

[mafreud]

@aalej Thank you!