7 replies

Handling Untagged Yieldable Errors in Go API Responses

Can we get a yieldable error that doesn't have to be tagged or can be tagged manually? I'm currently interacting with a Go API which returns a JSON object like this:

export class APIError extends Schema.Class<APIError>("APIError")({
    status_code: Schema.Number,
    description: Schema.String,
    service: Schema.String,
}) {}

export const FailedAPIResponse = Schema.Struct({
    ok: Schema.Literal(false),
    error: APIError,
    data: Schema.Null,
});

export class APIError extends Schema.Class<APIError>("APIError")({
    status_code: Schema.Number,
    description: Schema.String,
    service: Schema.String,
}) {}

export const FailedAPIResponse = Schema.Struct({
    ok: Schema.Literal(false),
    error: APIError,
    data: Schema.Null,
});

export class APIError extends Schema.Class<APIError>("APIError")({
    status_code: Schema.Number,
    description: Schema.String,
    service: Schema.String,
}) {}

export const FailedAPIResponse = Schema.Struct({
    ok: Schema.Literal(false),
    error: APIError,
    data: Schema.Null,
});

export class APIError extends Schema.Class<APIError>("APIError")({
    status_code: Schema.Number,
    description: Schema.String,
    service: Schema.String,
}) {}

export const FailedAPIResponse = Schema.Struct({
    ok: Schema.Literal(false),
    error: APIError,
    data: Schema.Null,
});

Handling Untagged Yieldable Errors in Go API Responses

Similar Threads

Similar Threads

Similar Threads