Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GraphqlErrorExtensions

import type { GraphqlErrorExtensions } from "https://googleapis.deno.dev/v1/firebasedataconnect:v1.ts";

GraphqlErrorExtensions contains additional information of GraphqlError.

interface GraphqlErrorExtensions {
code?:
| "OK"
| "CANCELLED"
| "UNKNOWN"
| "INVALID_ARGUMENT"
| "DEADLINE_EXCEEDED"
| "NOT_FOUND"
| "ALREADY_EXISTS"
| "PERMISSION_DENIED"
| "UNAUTHENTICATED"
| "RESOURCE_EXHAUSTED"
| "FAILED_PRECONDITION"
| "ABORTED"
| "OUT_OF_RANGE"
| "UNIMPLEMENTED"
| "INTERNAL"
| "UNAVAILABLE"
| "DATA_LOSS";
debugDetails?: string;
file?: string;
resource?: string;
}

§Properties

§
code?: "OK" | "CANCELLED" | "UNKNOWN" | "INVALID_ARGUMENT" | "DEADLINE_EXCEEDED" | "NOT_FOUND" | "ALREADY_EXISTS" | "PERMISSION_DENIED" | "UNAUTHENTICATED" | "RESOURCE_EXHAUSTED" | "FAILED_PRECONDITION" | "ABORTED" | "OUT_OF_RANGE" | "UNIMPLEMENTED" | "INTERNAL" | "UNAVAILABLE" | "DATA_LOSS"
[src]

Maps to canonical gRPC codes. If not specified, it represents Code.INTERNAL.

§
debugDetails?: string
[src]

More detailed error message to assist debugging. It contains application business logic that are inappropriate to leak publicly. In the emulator, Data Connect API always includes it to assist local development and debugging. In the backend, ConnectorService always hides it. GraphqlService without impersonation always include it. GraphqlService with impersonation includes it only if explicitly opted-in with include_debug_details in GraphqlRequestExtensions.

§
file?: string
[src]

The source file name where the error occurred. Included only for UpdateSchema and UpdateConnector, it corresponds to File.path of the provided Source.

§
resource?: string
[src]

Distinguish which schema or connector the error originates from. It should be set on errors from control plane APIs (e.g. UpdateSchema, UpdateConnector).