Skip to content

Conversation

@roguh
Copy link
Collaborator

@roguh roguh commented Jan 5, 2022

No description provided.

@roguh roguh self-assigned this Jan 5, 2022
@@ -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?

@@ -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.

const natsError = { ...natsErrorBase, code: "err", name: "err", message: "test error" };
try {
await testRequestMulti(3, 3, { natsError: natsError });
await testRequestMulti(3, 3, ({ natsError }));

Choose a reason for hiding this comment

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

Hm, I'm not sure you need the parentheses here, but if it works it's not a big deal.

const natsError = { ...natsErrorBase, code: "err", name: "err", message: "test error" };
try {
await testRequestMulti(3, 2, { natsError: natsError });
await testRequestMulti(3, 2, ({ natsError }));

Choose a reason for hiding this comment

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

See above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants