Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
CONTAINER_NAME=nats-request-multi-js_request-multi_1
CONTAINER_NAME=nats-multi-request-js-request-multi-1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not 100% sure what the naming conventions here would be, but if we're reversing the naming from request-multi to multi-request, shouldn't we do it in both parts of this name?

setup:
npm install

Expand Down
13 changes: 9 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,22 +1,27 @@
# nats-request-multi-js
# nats-multi-request-js

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It strikes me that the name is a little misleading, since technically it's a single request that could have multiple responses. But I'm not sure what a better name would be.


Library for making NATS requests that receive multiple responses.

<!--
TODO: upload to npm
## Installation
```
npm i nats-request-multi
npm i nats-multi-request
OR
npm i -S nats-request-multi
npm i -S nats-multi-request
```
-->

## Usage

Returns as soon as `expected` responses arrive.

```
import { connect } from 'nats'
import requestMulti from 'nats-request-multi'
import requestMulti from 'nats-multi-request'
async () {
const nc = connect()
Expand Down
Loading