Skip to content

docs: fix useSegmentEndpoints typo in README client options - #1322

Open
abueide wants to merge 1 commit into
masterfrom
fix/issue-1145
Open

docs: fix useSegmentEndpoints typo in README client options#1322
abueide wants to merge 1 commit into
masterfrom
fix/issue-1145

Conversation

@abueide

@abueide abueide commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

The README documented the client option as useSegmentEndpoint (singular), but the public API is useSegmentEndpoints (plural) -- see Config in packages/core/src/types.ts and its consumers in analytics.ts, SegmentDestination.ts and constants.ts.

Copying the name from the README fails to compile under TypeScript and is silently ignored in JavaScript, leaving proxy/cdnProxy endpoint suffixes unappended.

Prettier re-padded the whole table because the option name grew by one character; only the proxy, cdnProxy and useSegmentEndpoints rows changed substantively.

Fixes #1145

The README documented the client option as `useSegmentEndpoint` (singular),
but the public API is `useSegmentEndpoints` (plural) -- see `Config` in
packages/core/src/types.ts and its consumers in analytics.ts,
SegmentDestination.ts and constants.ts.

Copying the name from the README fails to compile under TypeScript and is
silently ignored in JavaScript, leaving proxy/cdnProxy endpoint suffixes
unappended.

Prettier re-padded the whole table because the option name grew by one
character; only the `proxy`, `cdnProxy` and `useSegmentEndpoints` rows
changed substantively.

Fixes #1145

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

Typo in useSegmentEndpoints client option in README

2 participants