Skip to content

chore(coverage): restore SDK statements coverage threshold to ≥50 #176

Description

@coderabbitai

Summary

The SDK statements coverage threshold in .testcoverage.yml was temporarily lowered from 50 → 40 in #174 ("refactor(table names): handle unsafe table names") to keep the PR scope manageable while new SDK endpoint/auth behavior was being shipped.

Goal

Restore the sdk statements threshold to 50 or higher once targeted SDK tests covering the new query-parameter endpoints and SSE auth changes are added.

Context

  • Lowered in: refactor(table names): handle unsafe table names #174 (comment: refactor(table names): handle unsafe table names #174 (comment))
  • Affected config key: suites.sdk in .testcoverage.yml
  • Files with new/changed SDK behavior that need test coverage:
    • clients/ts/src/table.ts — ingest/schema endpoints changed to ?table= query params
    • clients/ts/src/query-builder.ts — query endpoint changed to /v1/query?table=
    • clients/ts/src/stream/sse.ts — SSEOptions gained optional auth callback; reconnect/error handling expanded
    • clients/ts/src/client.ts — _createStream now passes auth to SSETransport

Requested by

@EricAndrechek

Activity

  1. coderabbitai commented on May 23, 2026

    @coderabbitai
    Author
    🔗 Related PRs

    #123 - fix(api): drop CORS credentials + skip same-origin decoration [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. coderabbitai commented on May 23, 2026

    @coderabbitai
    Author

    _createStream transport-selection test coverage

    Flagged in PR #174 (comment: #174 (comment)) — the _createStream transport-selection test suite was removed because the async SSE auth path broke the sync-vs-async detection hack used to distinguish SSE from WS.

    Specific cases that need to be covered once the testing approach is updated:

    • Auto mode, no auth → SSE transport is selected (EventSource constructor is called)
    • Auto mode, auth present → WS transport is selected (WebSocket constructor is called)
    • Forced SSE with auth → SSE transport is selected even when auth is set; auth token is injected as token query parameter in the SSE URL
    • Disconnect lifecycle → disconnect() closes the connection, decrements the active connection counter (clamped to 0), and emits a closed status

    Requested by @EricAndrechek.

  3. moved this from Backlog to Ready in WaveHouse Task Boardon May 24, 2026
  4. moved this from Ready to In progress in WaveHouse Task Boardon May 27, 2026
  5. moved this from In progress to In review in WaveHouse Task Boardon Jun 2, 2026
  6. added a commit that references this issue on Jun 2, 2026
    a4d72c1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/infraCI, build, deploy, Docker, releasearea/sdkTypeScript SDK (clients/ts/)chore

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions