Skip to content

Handle non-200 success codes#38

Open
kryptx wants to merge 2 commits intomasterfrom
handle-non-200-success-codes
Open

Handle non-200 success codes#38
kryptx wants to merge 2 commits intomasterfrom
handle-non-200-success-codes

Conversation

@kryptx
Copy link
Copy Markdown

@kryptx kryptx commented May 17, 2021

Allows the client to handle success codes other than 200.

@kryptx kryptx force-pushed the handle-non-200-success-codes branch from fa8abf4 to afddfdc Compare May 18, 2021 01:19
@Harmannz Harmannz self-requested a review May 18, 2021 01:28
Copy link
Copy Markdown

@Harmannz Harmannz left a comment

Choose a reason for hiding this comment

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

LGTM

Comment thread test/test_sailthru.js
})
.reply(201, {/* don't care about response */});

test.expect(2);
Copy link
Copy Markdown

@m1dcarry m1dcarry May 18, 2021

Choose a reason for hiding this comment

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

It's not clear to me as to why we are expecting 2 here? Shouldn't it be expecting 1 because we are only creating a single watch?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

The number is how many assertions nodeunit should expect. I've mainly just done this to follow the pattern elsewhere in this repo :)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Ah right okay. I misunderstood that! thanks

Copy link
Copy Markdown
Contributor

@ben833 ben833 left a comment

Choose a reason for hiding this comment

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

Please update the version before merging

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.

4 participants