nats-io / node-nats-streaming / 234

91%

master: 94%

Pull #96

travis-ci

- added (copied shamelessly) documentation from go-nats-streaming describing
how the client ping mechanism works.
- filled connection id in PubMsg
- added test to verify that PubMsg contains connection id and client id

Changed node-nats-streaming default for `maxReconnectAttempts` to be
infinite on connections created by the stan client (matching the
behaviour of the go-nats-streaming client)

Fixed tests that relied on `maxReconnectAttempts`.

142 of 193 branches covered (73.58%)

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

425 of 469 relevant lines covered (90.62%)

29.4 hits per line