node-opcua / node-opcua / 25751058326

92%

Build Type

push

github

Committed by erossignon

Commit Message

feat(client): propagate transportFactory option to ClientSecureChannelLayer

Threads the optional `transportFactory` added to
`ClientSecureChannelLayerOptions` in #1503 up to `OPCUAClientBaseOptions`,
so callers that construct clients through the standard
`OPCUAClient.create({...})` surface can substitute the transport
(e.g. a browser WebSocket transport) without reaching into the
secure-channel layer directly.

Purely additive:

- New optional field `transportFactory?: IClientTransportFactory` on
  `OPCUAClientBaseOptions`. When omitted, `ClientSecureChannelLayer`
  continues to fall back to `defaultClientTransportFactory` exactly as
  it does today.
- `ClientBaseImpl` stores the option in a new private
  `_transportFactory?: IClientTransportFactory` field and passes it
  through when constructing the channel.
- `node-opcua-transport` added as a direct dependency in
  `package.json` + `tsconfig.json` (previously transitive via
  `node-opcua-secure-channel`).

Unlocks the browser client package, which supplies a WebSocket-based
transport factory at construction time rather than requiring consumers
to construct a `ClientSecureChannelLayer` directly.

Test: `test/test_transport_factory_option.ts` — verifies
`OPCUAClient.create({ transportFactory })` is accepted at the type
level and at runtime, and that the option is optional (default path
preserved).

Coverage Stats

18612 of 22120 branches covered (84.14%)

14 of 14 new or added lines in 2 files covered. (100.0%)

5 existing lines in 1 file now uncovered.

162977 of 176783 relevant lines covered (92.19%)

468921.51 hits per line