nats-io / node-nats-streaming

91%

master: 94%

LAST BUILD ON BRANCH fix-97-98-99

branch: fix-97-98-99

CHANGE BRANCH

x

Reset

• fix-97-98-99
• 0.0.3
• 0.0.4
• ack-fix-15
• ackInbox-safety
• cncf
• coded-errors
• defer-subs-until-protocol
• dep-updates-release
• dev-deps-update
• doc
• duplicate-clientid-must-fail
• error-on-throw
• es6-lint
• fix-64
• fix-82
• fix-92
• fix-97-98
• fix-coveralls
• fix71
• master
• node-version-constraint
• node-version-fix
• node10-deprecations
• non-wip
• ping-doc
• port-option-fix
• protobuf-fix
• qlik-trial-client-side-pings
• reconnect-gives-nats-not-streaming-connection
• rename-publishasync-to-publish
• soulne4ny-master
• stan-nodejs-compat
• stan-ts-bindings
• sub-close
• subopts-time-fixes-17
• subscription-options-fixes
• typescript
• update-copyright
• update-to-reqone
• v.0.0.14
• v.0.0.50
• v0.0.28
• v0.0.40
• v0.0.51
• v0.0.52
• v0.0.8
• v0.1.0
• v0.2.0
• v0.2.2

Build # 241

Build Type

Pull #100

travis-ci

Committed by web-flow

Commit Message

FIX #99 - the properties `maxPingOut` and `pingInterval` shadow the properties
for plain nats client pings. To enable them to be configured separately, they
are renamed to `stanMaxPingOut` and `stanPingInterval`.

FIX #98 - node-nats options are not exposed in the index.d.ts, so typescript
aware editors/ides show errors on unknown properties.

FIX #97 - invalidated by renaming the options

Pull Request Pull Request #100: nats and stan properties

Run Details

142 of 193 branches covered (73.58%)

13 of 13 new or added lines in 1 file covered. (100.0%)

429 of 473 relevant lines covered (90.7%)

29.81 hits per line