Skip to content

refactor(grpc): drop storeResponseBody from GrpcMonitor#1413

Merged
sorccu merged 1 commit into
mainfrom
grpc-remove-store-response-body
Jul 17, 2026
Merged

refactor(grpc): drop storeResponseBody from GrpcMonitor#1413
sorccu merged 1 commit into
mainfrom
grpc-remove-store-response-body

Conversation

@danielpaulus

Copy link
Copy Markdown
Contributor

What

Removes storeResponseBody from the GrpcMonitor request. gRPC checks always store the response body now — the backend removed the per-check "store response body" toggle and no longer accepts or returns the field, so exposing it in the construct is misleading.

Changes

  • Drop storeResponseBody?: boolean from the GrpcRequest construct type.
  • Drop the field from the codegen emitter (grpc-request-codegen.ts), so checkly import no longer generates it.
  • Remove it from the affected construct fixtures.

Notes

Minor breaking type change: a project that explicitly set storeResponseBody in a GrpcMonitor will now get a TypeScript error. The field was already a no-op (the API ignores it), so removing it just surfaces that. No runtime behavior change — bodies are always stored.

gRPC checks always store the response body now — the backend removed the
per-check "store response body" toggle and no longer accepts or returns the
field. Remove it from the GrpcRequest construct type and the codegen emitter,
and drop it from the affected fixtures.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013AYwkvoaANQTH5dGStbBj2
@sorccu
sorccu force-pushed the grpc-remove-store-response-body branch from 83efb11 to 9fcfb16 Compare July 17, 2026 18:06
@sorccu
sorccu enabled auto-merge (squash) July 17, 2026 18:09
@sorccu
sorccu merged commit 3af93dd into main Jul 17, 2026
15 checks passed
@sorccu
sorccu deleted the grpc-remove-store-response-body branch July 17, 2026 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants