Skip to content

feat: improve error output by showing which URL caused the error#1735

Merged
paulmelnikow merged 4 commits intonock:betafrom
martinfrancois:patch-1
Oct 7, 2019
Merged

feat: improve error output by showing which URL caused the error#1735
paulmelnikow merged 4 commits intonock:betafrom
martinfrancois:patch-1

Conversation

@martinfrancois
Copy link
Copy Markdown
Contributor

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.

Copy link
Copy Markdown
Member

@paulmelnikow paulmelnikow left a comment

Choose a reason for hiding this comment

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

Thanks for this!

@paulmelnikow
Copy link
Copy Markdown
Member

I don't have access to push the suggested change, though if you accept it I can merge.

Co-Authored-By: Paul Melnikow <github@paulmelnikow.com>
@paulmelnikow paulmelnikow merged commit c0be8f8 into nock:beta Oct 7, 2019
@nockbot
Copy link
Copy Markdown
Collaborator

nockbot commented Oct 7, 2019

🎉 This PR is included in version 11.1.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@paulmelnikow
Copy link
Copy Markdown
Member

Oh gosh, this was targeting beta. What have I done?! 🤦‍♂

@paulmelnikow
Copy link
Copy Markdown
Member

@martinfrancois Would you mind opening a new PR targeting master?

@paulmelnikow
Copy link
Copy Markdown
Member

/cc @gr2m

@gr2m
Copy link
Copy Markdown
Member

gr2m commented Oct 7, 2019

I’d try to cherry pick the commits into a branch based of master and the send a PR

@martinfrancois
Copy link
Copy Markdown
Contributor Author

martinfrancois commented Oct 7, 2019

@paulmelnikow Sorry, didn't know this was supposed to go against master! Just reopened a PR with the change cherry picked against master (like suggested by @gr2m), see #1740

martinfrancois added a commit to martinfrancois/nock that referenced this pull request Oct 7, 2019
…k#1735)

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.
martinfrancois added a commit to martinfrancois/nock that referenced this pull request Oct 7, 2019
…k#1735)

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.
martinfrancois added a commit to martinfrancois/nock that referenced this pull request Oct 7, 2019
…k#1735)

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.
paulmelnikow pushed a commit that referenced this pull request Oct 7, 2019
…) (#1740)

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.
juninmd pushed a commit to juninmd/nock that referenced this pull request Mar 21, 2026
…k#1735) (nock#1740)

After getting an error in the interceptor, mentioning URL's need to start with a slash, it was difficult to find out which URL was causing the issue. With this change, since the URL is included in the error message, it's easier to troubleshoot the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants