Gap
ProbableExchange in core accepts a second constructor parameter wsConfig?: ProbableWebSocketConfig that controls WebSocket behaviour. Neither the TypeScript nor the Python SDK Probable class exposes this parameter.
Current state
Core (core/src/exchanges/probable/index.ts:50):
constructor(credentials?: ExchangeCredentials, wsConfig?: ProbableWebSocketConfig) {
super(credentials);
this.wsConfig = wsConfig;
...
}
TypeScript SDK (sdks/typescript/pmxt/client.ts:2690–2694):
export class Probable extends Exchange {
constructor(options: ExchangeOptions = {}) {
super("probable", options);
// wsConfig never accepted or forwarded
}
}
Python SDK (sdks/python/pmxt/_exchanges.py): the Probable class constructor accepts only api_key, api_secret, passphrase, private_key — no ws_config equivalent.
Expected behaviour
Both SDK Probable classes should accept a WebSocket configuration object (or equivalent fields) and forward them to the sidecar so that users can customise WebSocket endpoint, reconnect behaviour, etc.
Impact
WebSocket configuration for Probable is locked to sidecar defaults in both SDKs. Users who need to override WebSocket settings (e.g., for custom endpoints or timeouts) have no way to do so.
Gap
ProbableExchangein core accepts a second constructor parameterwsConfig?: ProbableWebSocketConfigthat controls WebSocket behaviour. Neither the TypeScript nor the Python SDKProbableclass exposes this parameter.Current state
Core (
core/src/exchanges/probable/index.ts:50):TypeScript SDK (
sdks/typescript/pmxt/client.ts:2690–2694):Python SDK (
sdks/python/pmxt/_exchanges.py): theProbableclass constructor accepts onlyapi_key,api_secret,passphrase,private_key— nows_configequivalent.Expected behaviour
Both SDK
Probableclasses should accept a WebSocket configuration object (or equivalent fields) and forward them to the sidecar so that users can customise WebSocket endpoint, reconnect behaviour, etc.Impact
WebSocket configuration for Probable is locked to sidecar defaults in both SDKs. Users who need to override WebSocket settings (e.g., for custom endpoints or timeouts) have no way to do so.