Skip to content

feat: add noop client implementation - #1365

Open
giortzisg wants to merge 1 commit into
feat/scopesfrom
scopes/noop-client
Open

feat: add noop client implementation#1365
giortzisg wants to merge 1 commit into
feat/scopesfrom
scopes/noop-client

Conversation

@giortzisg

@giortzisg giortzisg commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Description

This adds the Client interface and noop and default client implementations for the SDK. This better aligns the behavior with the current client spec and removes the need to always nil check any client.

Issues

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

  • Single entry: just write text
  • Multiple entries: use bullet points
  • Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

@giortzisg
giortzisg changed the base branch from feat/scopes to master July 20, 2026 08:33
@linear-code

linear-code Bot commented Jul 20, 2026

Copy link
Copy Markdown

GO-153

@giortzisg
giortzisg marked this pull request as ready for review July 20, 2026 11:24
Comment thread httpclient/sentryhttpclient.go
@giortzisg
giortzisg changed the base branch from master to feat/scopes July 21, 2026 12:36
@giortzisg
giortzisg force-pushed the scopes/noop-client branch from 4337b6c to 415d82c Compare July 23, 2026 08:45

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 415d82c. Configure here.

Comment thread client.go
// NewClient creates and returns a Client configured using ClientOptions.
func NewClient(options ClientOptions) (Client, error) {
return newClient(options)
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typed-nil Client on NewClient error

Medium Severity

NewClient returns (Client, error) by directly forwarding newClient, which returns a nil *defaultClient on failure. That produces a non-nil interface holding a typed nil, so client == nil is false while method calls panic. normalizeClient already guards this for hubs, but the public constructor still exposes it.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 415d82c. Configure here.

@giortzisg
giortzisg force-pushed the scopes/noop-client branch from 415d82c to 18b7a4a Compare July 30, 2026 20:45
Comment thread client_api.go
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.

Finalize noop client prerequisite

2 participants